Re: [ADMIN] ERROR: invalid memory alloc request size

2007-05-28 Thread Johann Spies
On Mon, May 28, 2007 at 11:18:37AM -0400, Tom Lane wrote: L> Alvaro Herrera <[EMAIL PROTECTED]> writes: > > Johann Spies wrote: > >> #3 0x005ff1c8 in perform_default_encoding_conversion ( > >> src=0x2b881e87f040 "\"2007-04-20\" \"18:07:06\" \"192.168.0.100\" \"73\" > >> \"http://www.kerkb

[ADMIN] Attempt to re-archive existing WAL logs after restoring from backup

2007-05-28 Thread Jon Colverson
Hello. I've been testing my DB backup and restore procedure and I've run into something I can't figure out. After recovering from a PITR backup, when I do another pg_start_backup PostgreSQL attempts to re-archive the last log again, which fails because it already exists in the archive. I'm ru

Re: [ADMIN] Return record on recursive call

2007-05-28 Thread Adam Radłowski
For info only (it's not exactly this same problem): This function looks like replacement of scroll cursor functionality. Cursors are working without problems. Adamn Michael Fuhr pisze: On Mon, May 28, 2007 at 05:06:55PM -0300, Alexander B. wrote: I am creating a function that when finished t

Re: [ADMIN] Return record on recursive call

2007-05-28 Thread Michael Fuhr
On Mon, May 28, 2007 at 05:06:55PM -0300, Alexander B. wrote: > I am creating a function that when finished the last level, should > return for each row. > I put raise notice to trace and the result is correct, but when I try to > execute, an error is showed. > > "ERRO: wrong record type supplied

[ADMIN] Return record on recursive call

2007-05-28 Thread Alexander B.
Hi, I am creating a function that when finished the last level, should return for each row. I put raise notice to trace and the result is correct, but when I try to execute, an error is showed. "ERRO: wrong record type supplied in RETURN NEXT" I created other functions the same way and worked, b

Re: [ADMIN] ERROR: invalid memory alloc request size

2007-05-28 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Johann Spies wrote: >> #3 0x005ff1c8 in perform_default_encoding_conversion ( >> src=0x2b881e87f040 "\"2007-04-20\" \"18:07:06\" \"192.168.0.100\" \"73\" >> \"http://www.kerkbode.co.za/kerkbode/images/blank.gif\\\"\"\n\"2007-04-20\"; >> \"18:0

Re: [ADMIN] ERROR: invalid memory alloc request size

2007-05-28 Thread Alvaro Herrera
Johann Spies wrote: > On Mon, May 21, 2007 at 10:40:40AM -0400, Tom Lane wrote: > > Well, if you aren't having any luck debugging it yourself, maybe you > > could put together a self-contained test case for someone else to > > reproduce the problem with? > > Hallo Tom, > > Sorry for the long dela

Re: [ADMIN] ERROR: invalid memory alloc request size

2007-05-28 Thread Johann Spies
On Mon, May 21, 2007 at 10:40:40AM -0400, Tom Lane wrote: > Well, if you aren't having any luck debugging it yourself, maybe you > could put together a self-contained test case for someone else to > reproduce the problem with? Hallo Tom, Sorry for the long delay. Maybe the following was what you

Re: [ADMIN] Syntax in postgresql.conf

2007-05-28 Thread Johann Spies
On Mon, May 28, 2007 at 09:05:37PM +1000, Phillip Smith wrote: > I believe you would need it to be: > listen_addresses = '192.168.0.1,localhost' > > ie, Don't close the quotes between your CSV's Thanks Phillip. That did it. Regards Johann -- Johann Spies Telefoon: 021-808 4036 Inf

Re: [ADMIN] Syntax in postgresql.conf

2007-05-28 Thread Phillip Smith
I believe you would need it to be: listen_addresses = '192.168.0.1,localhost' ie, Don't close the quotes between your CSV's On Mon, 2007-05-28 at 11:11 +0200, Johann Spies wrote: > listen_addresses = '192.168.0.1', 'localhost' > > I get > > $sudo /etc/init.d/postgresql-8.1 restart > * Res

[ADMIN] Syntax in postgresql.conf

2007-05-28 Thread Johann Spies
A comment in postgresql.conf on Debian says: " # comma-separated list of addresses; # defaults to 'localhost', '*' = all " But when I try listen_addresses = '192.168.0.1', 'localhost' I get $sudo /etc/init.d/postgresql-8.1 restart * Restarting PostgreSQL 8.1 databa