Re: [ADMIN] Strange deletion problem

2010-03-31 Thread John Lister
t off to shoot the developer in the leg as we speak.. John - Original Message - From: "robin" To: "John Lister" Cc: Sent: Wednesday, March 31, 2010 8:00 AM Subject: Re: [ADMIN] Strange deletion problem You could create a statement level delete trigger on the rele

Re: [ADMIN] Strange deletion problem

2010-03-31 Thread robin
You could create a statement level delete trigger on the relevant table, then get it to snapshot all the contents of the pg_stat_activity table (which will show all running queries) into some sort of log table. If you look at the plpgsql documentation (part of the postgresql manual for your releas

Re: [ADMIN] Strange deletion problem

2010-03-30 Thread John Lister
2010/3/30 John Lister Hi, I have a table which is constantly updated through out the day with no problems, I'm running Postgresql 8.3.8 in ubuntu karmic. However, within the last week for some reason overnight it is being emptied and I can't work out why. I've set log_min_duration_state

Re: [ADMIN] Strange deletion problem

2010-03-30 Thread Julius Tuskenis
hello, John 2010.03.30 10:57, John Lister rašė: - Is there any other statements that could be causing the rows to be removed that I've missed Please see |TRUNCATE.| - Is there anything that could be deleting them without generating a log entry for the statement? Don't think so... - Is it poss

Re: [ADMIN] Strange deletion problem

2010-03-30 Thread Szymon Guz
2010/3/30 John Lister > Hi, I have a table which is constantly updated through out the day with > no problems, I'm running Postgresql 8.3.8 in ubuntu karmic. However, within > the last week for some reason overnight it is being emptied and I can't work > out why. I've set log_min_duration_statem

[ADMIN] Strange deletion problem

2010-03-30 Thread John Lister
Hi, I have a table which is constantly updated through out the day with no problems, I'm running Postgresql 8.3.8 in ubuntu karmic. However, within the last week for some reason overnight it is being emptied and I can't work out why. I've set log_min_duration_statement to 0 so that postgresql du