> When using binary cursor to fetch contents of a bytea column into a variable
> set to NULL, the memory allocation relies on strlen to determine the amount
> of memory to allocate. If the data contains zeros, the memory allocated is
> too little to store the data.
And one more thank you for repor
The following bug has been logged online:
Bug reference: 4635
Logged by: Robert Walker
Email address: r.wal...@mtcworldwide.com
PostgreSQL version: 8.3.5
Operating system: WinXP SP2 32-bit
Description:postgres.exe crash when RAISE NOTICE during debugging of
PL/pgSQL f
Hello
2009/2/2 Tom Lane :
> "Martin Blazek" writes:
>> CREATE FUNCTION test() RETURNS integer AS $$
>> BEGIN
>> CREATE RULE "rule" AS ON INSERT TO "test" DO INSTEAD INSERT INTO "test"
>> VALUES (1);
>> END;$$ LANGUAGE plpgsql;
>
> Hm, I guess nobody ever tried to do that in plpgsql before. It's
Pavel Stehule writes:
> We should ignore INTO keyword when statement starts with CREATE
> keyword. This patch have to simple. I'll prepare it.
I'm already on it...
regards, tom lane
Index: gram.y
===
RCS fil
2009/2/2 Tom Lane :
> Pavel Stehule writes:
>> We should ignore INTO keyword when statement starts with CREATE
>> keyword. This patch have to simple. I'll prepare it.
>
> I'm already on it...
>
>regards, tom lane
ok
Regards
Pavel Stehule
>
> Index: gram.y
> ==
"Robert Walker" writes:
> I have a function that basically loops through a query and uses the results
> from that query to do an individual insert into another table, and if there
> is a unique violation, it simply raises a notice and continues on. When
> trying to debug the function within PgAdmi
The following bug has been logged online:
Bug reference: 4636
Logged by: Shane Caraveo
Email address: sha...@activestate.com
PostgreSQL version: 8.3.5
Operating system: osx 10.5 and linux
Description:dump/restore of table inheritance fails with serial
colums
Details:
"Martin Blazek" writes:
> CREATE FUNCTION test() RETURNS integer AS $$
> BEGIN
> CREATE RULE "rule" AS ON INSERT TO "test" DO INSTEAD INSERT INTO "test"
> VALUES (1);
> END;$$ LANGUAGE plpgsql;
Hm, I guess nobody ever tried to do that in plpgsql before. It's
taking the INTO as starting a clause
Sorry, for the long time before I answer, but this email, like others, was
caught by my spam filter. Spamassassin doesn't like mail hubs calling
themselves localhost. Sigh.
> Support for %s format is broken in PGTYPEStimestamp_defmt_asc.
Fixed in CVS HEAD. Thanks for the report.
Michael
--
Mic
