We have a huge database which must be backed up every day with pg_dump. The problem is, it takes around half an hour to produce the dump file, and all other processes on the same box are starved for cycles (presumably due to I/O) during the dump. It's not just an inconvenience, it's now evolved
We have this simple query:
select status, count(*) from customer group by status;
There is already a btree index on status, but, the customer table is huge, and this query must be executed very frequently... an "explain" on this query shows that it is quite costly (and we notice it runs slowl
subscribe
We have a running server (v7.3) which, over time, seems to accumulate a
bunch of "stuck" PostgreSQL instances which appear to be dead inside of
a transaction. For example, "ps" reveals many of these:
postgres 17683 0.0 0.4 7376 1032 ?SNov13 0:21 postgres:
bryan sourceid 127.0.0.1
Forgive me if I am missing the obvious, but can someone please tell me how
to show a list of triggers, or the code in a specific trigger, via the pgsql
utility?
Thank you,
Bryan
Please forgive my newbieness but I am extremely new to both Postgresql AND
Linux. I've been a consultant for 6 years working mostly on Microsoft
platforms (NT, MSSQL). I have developed many data-driven websites using
WinNT/IIS/ASP/MSSQL. Now, getting sick of MS and being enamored with the
whole Op
