Would it be possible to create a constraint that makes rows of a certain table impossible to delete? Perhaps by adding a constraint of that type, I would be able to get some more logging of the event that makes the rows disappear? When they were getting blown away, the constraint would prevent it and thus I would hope, some event would be logged. Possible? Ill-advised? > From: Lincoln Yeoh <lyeoh@xxxxxxxxxxxxx> > Date: Sun, 07 May 2006 17:48:32 +0800 > To: HH <lists@xxxxxxxxxxxxxxxxx> > Cc: PostgreSQL <pgsql-general@xxxxxxxxxxxxxx> > Subject: Re: [GENERAL] Can't Figure Out Where Rows Are Going > > Are the relevant COMMITs appearing in the log? > > If the commits fail for whatever reason does/can the application (and > postgresql) log that? > > If the commits are successful then you shouldn't have to need to look for > roll-backs. > > It might be a good idea for teh webapp to log unsuccessful commits. And > maybe even log important commits that are successful. > > Regards, > > Link. > > At 05:30 PM 5/6/2006 -0700, HH wrote: > >> Thanks for taking the time to reply. >> >> If that was occurring, would the log show it? I don't see any sign of a >> roll-back occurring in the log and when I run the queries in psql, they seem >> to complete properly. > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq
