I would like to identify the objects which all of a sudden are frowing
at the high growth rate by using the filename (which I assune is the
OID). I have looked at the pg_catalog schema to see if I could see an
obvious way to do this, but to no avail. Furthermore, I hate to keep
bothering the n
I have a very strange situation where all of a sudden my database growth
has increased dramatically.
I made some schema changes, bit these were made to some tables which do
not have the massive insertion rate (a few fields were changed from
varchar to inet data types.
The tables which have the mass
The postgresql parameter explanation for work_mem say :-
"Another way to set this value is to monitor the Postgres temp files(in PGDATA/base/DB_OID/pgsql_tmp) and adjust sort_memupward if you see a lot of queries swapping from these temp files."
...but I can't find pgsql_tmp in my v8.1.4 instal
adey wrote:
If you turn WAL logging off (via fsynch parameter in .conf), it is my
understanding that you will no longer log database updates, and will
therefore not be able to recover any uncommitted transactions in the
event of failure, (which seems contradictory to database practice).
You
If you turn WAL logging off (via fsynch parameter in .conf), it is my understanding that you will no longer log database updates, and will therefore not be able to recover any uncommitted transactions in the event of failure, (which seems contradictory to database practice).
Gut feel to me says
On 7/11/06, Burbello <[EMAIL PROTECTED]> wrote:
I need to test and create a procedure to restoredatabases.Why not just use pg_dump?See http://manual.intl.indoglobal.com/ch06s07.html
- it's really easy. This is how we copy from production to testing and development and how we do nightly backups. =
unsubscribe pgsql-admin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
unsubscribe pgsql-admin
unsubscribe pgsql-admin
