postgresql-9.1

If I have a query like SELECT date_trunc('day', assigndate)e, count(CASE WHEN a.assigneeid = 65548 AND a.assigneeid IN (SELECT userid FROM groupmembers WHERE groupid = 65553) THEN 1 ELSE NULL END) assigned, count(CASE WHEN a.assigneeid = 65548 AND a.completedtime IS NOT NULL AND a.assigneeid IN (SELECT userid FROM groupmembers WHERE groupid = 65553) THEN 1 ELSE NULL END) completed FROM ASSIGNMENT a WHERE assigndate > CURRENT_TIMESTAMP - interval '20 days' GROUP BY date_trunc('day',assigndate); The subquery in question is SELECT userid FROM groupmembers WHERE groupid = 65553 then since the

When trying to use the WHERE NOT EXISTS clause to prevent adding a row with a duplicate value in the column age , I get the error syntax error at or near "WHERE" . Why did it throw a syntax error? I'm using Postgresql 9.1. SQL INSERT INTO live.users ("website", "age") values ('abc', '123') WHERE NOT EXISTS (SELECT age FROM live.users WHERE age = 123); Error ERROR: syntax error at or near "WHERE" LINE 6: WHERE NOT EXISTS (SELECT age FROM live.users W... Do instead: INSERT INTO live.users ("website", "age") SELECT 'abc', 123 WHERE NOT EXISTS (SELECT age FROM live.users WHERE age = 123); INSERT

I have a cube that has 8 dimensions. I want to do nearest neighbor matching. I'm totally new to postgresql. I read that 9.1 supports nearest neighbor matching on multidimensions. I'd really appreciate if someone could give a complete example: How to create a table with the 8D cube ? Sample Insert Lookup - exact matching Lookup - nearest neighbor matching Sample Data: For simplicity sake, we can assume that all the values range from 0-100. Point1: (1,1,1,1, 1,1,1,1) Point2: (2,2,2,2, 2,2,2,2) Look up value: (1,1,1,1, 1,1,1,2) This should match against Point1 and not Point2. Refs: What's_new_in

Getting problem when taking backup on database contains around 50 schema with each schema having around 100 tables. pg_dump throwing below error suggesting that to increase max_locks_per_transaction . pg_dump: WARNING: out of shared memory pg_dump: SQL command failed pg_dump: Error message from server: ERROR: out of shared memory HINT: You might need to increase max_locks_per_transaction. pg_dump: The command was: SELECT tableoid, oid, prsname, prsnamespace, prsstart::oid, prstoken::oid, prsend::oid, prsheadline::oid, prslextype::oid FROM pg_ts_parser An updated of max_locks_per_transaction to

Our postgres data folder was installed on a drive with very limited space. I'm now trying to move it over to a newly mounted drive (more space). I've followed several blog posts and they all say... stop service copy data cluster update postgresql-9.1 file (PGDATA=) restart service The service starts but when I go to connect, it gives me "could not connect to server: Connection refused" I tried telnet-ing to port 5432 and nothing. Here is the link to what I've been trying: http://www-01.ibm.com/support/docview.wss?uid=swg21324272 Thanks everyone for your help. Looks like the problem was with

I have a Java app that uses a Postgres database and I'm trying to introduce PGPool in order to scale up my database. I'm running into a problem where Postgres throws the following error: unnamed prepared statement does not exist . After cranking up the logging on Postgres I see the following stuff happening for every select statement my app executes: EDTLOG: 00000: duration: 7.585 ms parse <unnamed>: "my select statement here" EDTLOG: 00000: duration: 0.088 ms bind <unnamed>: "my select statement here" EDTLOG: 00000: duration: 79.014 ms execute <unnamed>: "my select statement here" But

I have one table in which I would like only one entry . So if someone is trying to insert another row it shouldn't be allowed, only after someone deleted the previously existing row. How do I set a rule for a table like this? Erwin Brandstetter A UNIQUE constraint allows multiple rows with NULL values, because two NULL values are never considered to be the same. Similar considerations apply to CHECK constraints. They allow the expression to be TRUE or NULL (just not FALSE ). Again, NULL values get past the check. To rule that out, the column must be defined NOT NULL . Or make it the PRIMARY

I'd like to know if there are some benchmark to compare how much cost insert some check constraints on a table of 60 columns where on 20 i'd like to insert a constraints of NotEmpty and on 6 rows NotNull. My case is that i have on my table Empty values and Null values (that in my case means always "no data"). I'd like to unify that data values with just one. That's why I'm thinking to insert NotEmpty constraints on columns, because as i have read null value are not heavy (in byte size) as like empty values (and respect his real meaning). But from other side NotNull Constraint are more deep

Is it possible to order the results of a PostgreSQL query by a title field that contains characters like [](),; etc but do so ignoring these punctuation characters and sorting only by the text characters? I've read articles on changing the database collation or locale but have not found any clear instructions on how to do this on an existing database an on a per-column basis. Is this even possible? If you want to have this ordering in one particular query you can ORDER BY regexp_replace(title, '[^a-zA-Z]', '', 'g') It will delete all non A-Z from sting and order by resulting field. Erwin