Re: [BUGS] BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342

2011-03-17 Thread Tambet Matiisen
On 16.03.2011 17:09, Kevin Grittner wrote: Tambet Matiisen wrote: Pre-live database is restored from live database dump every night. How is that done? A single pg_dump of the entire live database restored using psql? Are both database servers at the same PostgreSQL version? Yes, I use pg

Re: [BUGS] BUG #5934: postgresql.conf: optional equal sign

2011-03-17 Thread Frederic Junod
On Thu, Mar 17, 2011 at 12:07 AM, Euler Taveira de Oliveira wrote: > Em 16-03-2011 12:25, Frederic Junod escreveu: >> >> "Error: Invalid line 502 in /etc/postgresql/8.4/main/postgresql.conf: >> »listen_addresses  '*'«" >> > AFAICS it is a Debian bug not a PostgreSQL one. I already hit it once but

Re: [BUGS] BUG #5929: ERROR: found toasted toast chunk for toast value 260340218 in pg_toast_260339342

2011-03-17 Thread Tambet Matiisen
On 16.03.2011 22:29, Kevin Grittner wrote: Tambet Matiisen wrote: Yes, I use pg_dump on live server and the result is rdiff-backupped into development server. Whole SQL dump is 12G without compression and the rdiff delta is about 10-20MB every day. Then I drop pre-live database on development s

Re: [BUGS] BUG #5842: Memory leak in PL/Python when taking slices of results

2011-03-17 Thread Alvaro Herrera
Excerpts from Daniel Popowich's message of mar ene 18 13:30:04 -0300 2011: > I traced the bug to PLy_result_slice() in src/pl/plpython/plpython.c. That > function calls the python API function PyList_GetSlice() and erroneously > increments the reference count before returning the result to the ca

[BUGS] BUG #5935: Log lotation not working for default log format

2011-03-17 Thread Brad Nicholson
The following bug has been logged online: Bug reference: 5935 Logged by: Brad Nicholson Email address: bnichol...@hp.com PostgreSQL version: 9.0.3 Operating system: CentOS Release 5.5 Description:Log lotation not working for default log format Details: PostgreSQL 9.

Re: [BUGS] BUG #5935: Log lotation not working for default log format

2011-03-17 Thread Korry Douglas
What would you expect the new log file to be named? Your log_filename is set to postgresql-%a.log. The %a part expands to the current day of the week. If it's Thursday and you already have a file for Thursday, what would the new file name be? -- Korry > The following bug has

Re: [BUGS] BUG #5935: Log lotation not working for default log format

2011-03-17 Thread Nicholson, Brad (Toronto, ON, CA)
You could appending something onto the logfile to differentiate it, but I can understand why you wouldn't want to as that would change the filename format. If this is the case, the call to pg_rotate_logfile() should return false. I'd also say that starting up and allowing a file size based rotat

Re: [BUGS] BUG #5935: Log lotation not working for default log format

2011-03-17 Thread Korry Douglas
> You could appending something onto the logfile to differentiate it, but I can > understand why you wouldn't want to as that would change the filename format. > > If this is the case, the call to pg_rotate_logfile() should return false. pg_rotate_logfile() doesn't actually rotate the log file,