Joost Kraaijeveld wrote:
Hi all,
Thanks for looking into it. The problem is solved: on both machines
there appeared to be a hung-up backup process that locked PostgreSQL.
If that's a file-level backup, you'll want to exclude the PG directories
(or stop the database while the backup occurs).
Hi all,
Thanks for looking into it. The problem is solved: on both machines
there appeared to be a hung-up backup process that locked PostgreSQL.
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl
---
Joost Kraaijeveld wrote:
It looks to me that you may be a victim of the bug patched in
>> http://archives.postgresql.org/pgsql-committers/2007-01/msg00214.php.
Tom, whatever happened about a backpatch for that one?
>>> It's applied.
>>>
>> http://developer.postgresql.org/cvsweb.cgi/p
On Mon, 2007-03-12 at 15:37 +0100, Magnus Hagander wrote:
> On Mon, Mar 12, 2007 at 10:13:48AM -0400, Tom Lane wrote:
> > Magnus Hagander <[EMAIL PROTECTED]> writes:
> > > It looks to me that you may be a victim of the bug patched in
> > >
> http://archives.postgresql.org/pgsql-committers/2007-01/m
On Mon, Mar 12, 2007 at 10:13:48AM -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > It looks to me that you may be a victim of the bug patched in
> > http://archives.postgresql.org/pgsql-committers/2007-01/msg00214.php.
> > Tom, whatever happened about a backpatch for that o
On Mon, 2007-03-12 at 10:13 -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > It looks to me that you may be a victim of the bug patched in
> > http://archives.postgresql.org/pgsql-committers/2007-01/msg00214.php.
> > Tom, whatever happened about a backpatch for that one?
>
Magnus Hagander <[EMAIL PROTECTED]> writes:
> It looks to me that you may be a victim of the bug patched in
> http://archives.postgresql.org/pgsql-committers/2007-01/msg00214.php.
> Tom, whatever happened about a backpatch for that one?
It's applied.
http://developer.postgresql.org/cvsweb.cgi/pgsq
On Mon, Mar 12, 2007 at 02:46:22PM +0100, Joost Kraaijeveld wrote:
> On Mon, 2007-03-12 at 14:39 +0100, Magnus Hagander wrote:
>
> > What version of PostgreSQL is this?
> >
> Oh, forgotten: 8.1.x with no upgrade option (company policy)
It looks to me that you may be a victim of the bug patched i
On Mon, 2007-03-12 at 14:39 +0100, Magnus Hagander wrote:
> What version of PostgreSQL is this?
>
Oh, forgotten: 8.1.x with no upgrade option (company policy)
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.a
On Mon, Mar 12, 2007 at 02:20:44PM +0100, Joost Kraaijeveld wrote:
> Hi,
>
> The PostgreSQL of a customer database (running on Windows 2003) crashed
> and wrote the messages below in the logfile. According to the customer
> the drives are working OK, partitions are not full and nothing has
> chang
Hi,
The PostgreSQL of a customer database (running on Windows 2003) crashed
and wrote the messages below in the logfile. According to the customer
the drives are working OK, partitions are not full and nothing has
changed in the permissions. The customer could restart the PostgreSQL
service manual
11 matches
Mail list logo
