Julinho wrote:
I would like to sugest a control panel ou icontray interface to postgre
like service manager in MSSQL (icontray) or the Firebird Server manager
(control panel).
It would be very nice to control de service!
I never understood what that tray icon should be good for (beyond
filling u
Hello,
I am just starting to test out Postgres8 beta1 and notice that the
deadlock detection mechanism is not working (under windows XP pro with
service pack 1). I am using the version of Postgres built by the
PGFoundry project, and have it installed as a service.
To produce the bug I simply lau
"Steve McWilliams" <[EMAIL PROTECTED]> writes:
> I am just starting to test out Postgres8 beta1 and notice that the
> deadlock detection mechanism is not working (under windows XP pro with
> service pack 1). I am using the version of Postgres built by the
> PGFoundry project, and have it installed
> "Steve McWilliams" <[EMAIL PROTECTED]> writes:
>> I am just starting to test out Postgres8 beta1 and notice that the
>> deadlock detection mechanism is not working (under windows XP pro with
>> service pack 1). I am using the version of Postgres built by the
>> PGFoundry project, and have it in
Andreas Pflug wrote:
> Julinho wrote:
>
>> I would like to sugest a control panel ou icontray interface to
>> postgre like service manager in MSSQL (icontray) or the Firebird
>> Server manager (control panel).
>> It would be very nice to control de service!
>
>
> I never understood what that tray i
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> A reasonable theory about this would be that the timer interrupt isn't
>> firing. Does "statement_timeout" work either?
> Bugger. I've found the reason for this - statement_timeout was also
> broken. This was broken by the change of how signals are
> Just outta curiosity, why wasn't that detected by the
> regression tests?
> There is a test that depends on statement_timeout working ...
For the record, this was reported here a couple days after the plpgsql test
was changed:
http://archives.postgresql.org/pgsql-hackers/2004-08/msg00482.php
