6,439 reputation
31436
bio website
location Berlin, Germany
age 38
visits member for 2 years, 6 months
seen 6 hours ago

Jul
3
comment Postgres : Executing SELECT within a transaction does not return most recent rows
I think your problem is simply having a BEFORE trigger - it fires before the row is inserted which cannot appear in the view yet. Change it to AFTER and (after considering @CraigRinger's suggestion) you are done.
Jun
30
comment Advice to choose the best tool
Well, in 30 seconds PostgreSQL can return you all the 10M rows, joined between the two tables, I guess. There is something really bad going on. So, you have to figure out where exactly you loose all that time and do something to it. It may be the DB schema design, the lack of indexes, slow/unreliable network connection, bad application design and about a million other things.
Jun
26
comment Inner joins take too long
I guess I'd try to push the query into a CTE (WITH query), without the join on order_item_attribute, then join that table in the main query. Also, a multicolumn index on order_header (order_id, status_id) may help.
Jun
25
comment use domains in multiple schemas
Basically you have to decide the same for every object. When you don't specify the schema, the system will call search_path to help and pick the first schema from there (more or less).
Jun
25
comment use domains in multiple schemas
Are you looking for your_schema.your_domain?
Jun
25
comment Slow search times with functions despite index?
Do you actually have a reason for using a cursor? Why not simply return the results from RETURN QUERY (or a SQL function)? Google for RBAR.
Jun
20
comment Issue working with Postgres on Windows
Try to open the dump in query editor and run from there or really do it from the command line. I'm not sure what that console can or cannot do.
Jun
20
comment Issue working with Postgres on Windows
Which OS, exactly what command issued? What do you see in the dump if you visit it with an editor?
Jun
20
comment Issue working with Postgres on Windows
Do you try to run psql from pgAdmin? At least what you write suggests that. It won't work. You should run it from the command line or open the dump in the pgAdmin query tool and run it from there.
Jun
19
comment Postgres resource management
Nobody will able to answer you without knowing about your databases some details, like how many connections they get, how much memory/temp disk space they use, how they are interconnected by queries/application logic and so on. From a pure resource consumption the best thing to have is one physical machine for every single database but there are other factors, too.
Jun
19
comment Does PostgreSQL support multi-threaded replication?
@ypercube Thanks. I don't know if the PostgreSQL WAL solution allows out-of-order replication or parallelizing in-order replication is a big win. Any clue?
Jun
19
comment Does PostgreSQL support multi-threaded replication?
What exactly you mean by multi-threaded? More than one slaves? Or replicating to the same slave with more than one worker?
Jun
18
comment Difference between pg_column_size(table.*) and pg_column_size(table.col1) + pg_column_size (table.col2)
@luannnh Now that you cited it, I realized that I had written 4k instead of 4. Fixed.
Jun
17
comment Official PostgreSQL Capitalization conventions
Well, camelCase and PascalCase in PostgreSQL are a bit painful. You have to quote these if you really want to have the names like that, otherwise the system silently lowercase them (I nearly wrote decapitalize, whatever associations it may arouse).
Jun
16
comment database not restoring from dump file
In your command for restoring, you don't specify which DB to use. In this case, psql connects to the database named as the user, in this case postgres. Your objects are created there.
Jun
16
comment Using the correct postgres server
It's not very likely, 8.4 usually creates its files in a .../8.4/... directory. Which version did you install recently?
Jun
16
comment Using the correct postgres server
Hm. That means that you have to find out where the old data files are.
Jun
16
comment Postgres reported table / db size varies wildly from dump size
This is definitely not true. It very much depends on the data. I've done a short test on one of my toy databases, it reports 8554 kB in psql, the text format dump is 2279 kB.
Jun
16
comment Using the correct postgres server
You have to su - postgres and start the server like that. The root user is not allowed to do that for security reasons.
Jun
16
comment Postgres reported table / db size varies wildly from dump size
Your question related to LOBs is answered here: stackoverflow.com/questions/18636850/…