I have a pg dump (custom format, column-inserts) which I'm restoring on an
existing DB as
" /usr/bin/pg_restore -a -v -d db1 -F c " and the input is passed in from
stdin. It warns on a couple of existing rows, but completes successfully
with "WARNING: errors ignored on restore: 5".
However, this re
Based on my config, what is the max size this directory is expected to grow
? And how can I check whether this recycle/removal is happening fine ?
On Tue, Feb 28, 2017 at 10:08 AM, Michael Paquier wrote:
> On Tue, Feb 28, 2017 at 1:20 PM, dhanuj hippie
> wrote:
> > So does it wo
So does it work like - it can go upto 16MB*1024 times which is 16GB, and
then this will be cleaned up automatically ?
On Tue, Feb 28, 2017 at 9:47 AM, dhanuj hippie
wrote:
> psql (9.3.5)
> wal_keep_segments = 1024
>
> On Tue, Feb 28, 2017 at 9:16 AM, Rob Sargent
> wrote:
>
psql (9.3.5)
wal_keep_segments = 1024
On Tue, Feb 28, 2017 at 9:16 AM, Rob Sargent wrote:
>
> > On Feb 27, 2017, at 8:33 PM, dhanuj hippie
> wrote:
> >
> > Hi,
> >
> > I have a postgres cluster running in hot_standby. I see the pg_xlog is
> growing over t
Hi,
I have a postgres cluster running in hot_standby. I see the pg_xlog is
growing over time (may files of size 16 MB each). The replication lag is
very less ~2kB, and never goes into a bad state.
I'm manually resetting this once a while using pg_resetxlog command.
Is there a way to understand why
Hi,
I have a postgres-9.6 server running with SSL enabled, and I have setup the
certificates as per documentation. But currently the key file is not
protected by passphrase. Does postgres provide a way to use passphrase
protected keys ?
Thanks
Dhanuj
Hi,
I have a pg backup created using pg_dump custom format. I'm trying to
restore into a DB which already has some data, using pg_restore data-only.
This fails in scenarios where same data (some rows) is present in DB as
well as dump. Is there a way to ignore such rows and proceed with restoring
th
