On Fri, Jan 29, 2010 at 12:03 AM, Mason Hale wrote:
> Of course the best solution is to avoid this issue entirely. Something as
> easy to miss as file permissions should not cause data corruption,
> especially in the process meant to fail over from a crashing primary
> database.
I believe that su
Il giorno 28/gen/10, alle ore 18:32, Bruce Momjian ha scritto:
Giorgio Valoti wrote:
Il giorno 28/gen/10, alle ore 17:28, Tom Lane ha scritto:
Giorgio Valoti writes:
months ago I?ve submitted a bug (#4953). Is there a way to know its
status and if it will be fixed?
[ looks up 4953... ]
On Thu, 2010-01-28 at 18:15 +0100, Giorgio Valoti wrote:
> Ok, sorry for the silly question but is the xml core support
> comparable to contrib/xml2? Is it already there in 8.4 or is scheduled
> for 8.5?
It's available in 8.3 and later. The documentation can be found here:
http://www.postgres
Giorgio Valoti wrote:
>
> Il giorno 28/gen/10, alle ore 17:28, Tom Lane ha scritto:
>
> > Giorgio Valoti writes:
> >> months ago I?ve submitted a bug (#4953). Is there a way to know its
> >> status and if it will be fixed?
> >
> > [ looks up 4953... ] Oh, the contrib/xml2 memory management mess
Il giorno 28/gen/10, alle ore 17:28, Tom Lane ha scritto:
Giorgio Valoti writes:
months ago Ive submitted a bug (#4953). Is there a way to know its
status and if it will be fixed?
[ looks up 4953... ] Oh, the contrib/xml2 memory management mess :-(.
Don't hold your breath waiting for a fi
Giorgio Valoti writes:
> months ago Ive submitted a bug (#4953). Is there a way to know its
> status and if it will be fixed?
[ looks up 4953... ] Oh, the contrib/xml2 memory management mess :-(.
Don't hold your breath waiting for a fix for that. That code is on its
way out anyway, and so no
Hello Heikki --
Thank you for investigating this issue and clearing up this mystery.
I do not believe it is obvious that the postgres process needs to be able to
remove the trigger file.
My naive assumption was that the trigger file was merely a flag to signal
that recovery mode needed to be stop
So how can emedded SQL in C to get the record type which returning from
plpgsql function?
I have tested as following code:
CREATE OR REPLACE FUNCTION test4(IN a integer, OUT b int,OUT c int) AS
$BODY$ declare begin b:=100; c:=200; return; END $BODY$
LANGUAGE 'plpgsql' VOLATILE
COST 100;
Hi,
months ago I’ve submitted a bug (#4953). Is there a way to know its
status and if it will be fixed?
Thank you in advance
--
Giorgio Valoti
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Mason Hale wrote:
> ERROR: could not remove "/tmp/pgsql.trigger.5432": Operation not
> permittedtrigger file found
>
> ERROR: could not remove "/tmp/pgsql.trigger.5432": Operation not permitted
>
> This file was not looked until after the attempt to recover was
> aborted. Clearly the permission
10 matches
Mail list logo