currently or previously.
Searching through the archives, I have only stumbled upon a post from 2003
about a similar issue
(http://archives.postgresql.org/pgsql-admin/2003-08/msg00239.php) which might
be connected, however, since the reporter gave up quickly, the issue remained
unsolved.
H
e note, obviously, the Windows dump came out alright because it was
from the proper database, not the replicated copy.
Best regards,
Marek Kielar
Dnia 27 lipca 2012 4:46 Adrian Klaver napisał(a):
> On 07/26/2012 04:09 PM, Marek Kielar wrote:
> > Hi,
> >
> > we are using &q
Hi,
Dnia 28 lipca 2012 1:10 Adrian Klaver napisał(a):
> What where the deleted files?
>WAL, Logs, other?
> What type of WAL replication are you doing?
>Streaming, log shipping, etc?
> What are your settings for the WAL replication?
>In particular wal_keep_segments ?
> Is the WAL rep
Hi,
to complement information from the previous message:
Dnia 29 lipca 2012 12:29 Marek Kielar napisał(a):
> Hi,
>
>
> Dnia 28 lipca 2012 1:10 Adrian Klaver napisał(a):
>
> > What where the deleted files?
> >WAL, Logs, other?
>
>
> at this tim
ck;t
virtualxid;3/667499;3/667499;25145;ExclusiveLock;t
relation;11874;1098585/101817;25171;AccessShareLock;t
virtualxid;85/101817;;;;;85/101817;25171;ExclusiveLock;t
(4 rows)
We are again approaching slowly the point that the server restart will be
needed. If / when this happens,