Re: [BUGS] 9.1 plperlu bug with null rows in trigger hash

2011-05-27 Thread Alvaro Herrera
Excerpts from Alex Hunsaker's message of vie may 27 12:14:25 -0400 2011: > On Mon, May 23, 2011 at 20:08, Greg Sabino Mullane wrote: > > On Mon, May 23, 2011 at 05:04:40PM -0600, Alex Hunsaker wrote: > > ... > >> Greg, can you confirm the attached fixes it for you? > > > > Yes, seems to have done

Re: [BUGS] BUG #6044: Access violation on XML decl with standalone

2011-05-27 Thread Tom Lane
"Christopher Dillard" writes: > In PostgreSQL 8.4.8, the function "xml_recv" (in > src/backend/utils/adt/xml.c) calls the function "parse_xml_decl", passing > NULL for the final "standalone" parameter. However, "parse_xml_decl" does > not check for standalone==NULL, and blindly sets "*standalone

Re: [BUGS] 9.1 plperlu bug with null rows in trigger hash

2011-05-27 Thread Alexey Klyukin
On May 27, 2011, at 7:14 PM, Alex Hunsaker wrote: > On Mon, May 23, 2011 at 20:08, Greg Sabino Mullane wrote: >> On Mon, May 23, 2011 at 05:04:40PM -0600, Alex Hunsaker wrote: >> ... >>> Greg, can you confirm the attached fixes it for you? >> >> Yes, seems to have done the job, thank you. > >

[BUGS] BUG #6044: Access violation on XML decl with standalone

2011-05-27 Thread Christopher Dillard
The following bug has been logged online: Bug reference: 6044 Logged by: Christopher Dillard Email address: csdill...@gmail.com PostgreSQL version: 8.4.8 Operating system: Windows Description:Access violation on XML decl with standalone Details: Hello, In PostgreSQ

[BUGS] UTC4115FATAL: the database system is in recovery mode

2011-05-27 Thread Mathew Samuel
Hi, I see the following error as found in pg.log: UTC4115FATAL: the database system is in recovery mode Actually that message was logged repeatedly for about 4 hours according to the logs (I don't have access to the system itself, just the logs). Leading up to that error were the following in

Re: [BUGS] 9.1 plperlu bug with null rows in trigger hash

2011-05-27 Thread Alex Hunsaker
On Mon, May 23, 2011 at 20:08, Greg Sabino Mullane wrote: > On Mon, May 23, 2011 at 05:04:40PM -0600, Alex Hunsaker wrote: > ... >> Greg, can you confirm the attached fixes it for you? > > Yes, seems to have done the job, thank you. Thanks for testing! [ Does a little dance to try and attract a

Re: [BUGS] BUG #6043: Compilation PLpgsql Succesful but execution bad

2011-05-27 Thread Heikki Linnakangas
On 27.05.2011 17:05, Emanuel wrote: postgres=# CREATE OR REPLACE FUNCTION p_() RETURNS TABLE (i int) AS $$ DECLARE BEGIN SELECT * FROM p; --<<<-- here must ne RETURN QUERY .. END; $$ LANGUAGE plpgsql; CREATE FUNCTION postgres=# select p_(); ERROR: query has no destination for result data HIN

[BUGS] BUG #6043: Compilation PLpgsql Succesful but execution bad

2011-05-27 Thread Emanuel
The following bug has been logged online: Bug reference: 6043 Logged by: Emanuel Email address: postgres@gmail.com PostgreSQL version: 9.1 beta Operating system: Ubuntu 10.04 2.6.31 Description:Compilation PLpgsql Succesful but execution bad Details: postgres=#

Re: [BUGS] BUG #6042: unlogged table with Streaming Replication

2011-05-27 Thread Simon Riggs
On Fri, May 27, 2011 at 7:15 AM, Tomonari Katsumata wrote: > I've thought that if there are no standby, > the primary would behave like stand-alone... > sorry, this is my misunderstanding. It is a common misunderstanding. The programmed behaviour leads to the most trusted level of robustness. -