g the application.
Thanks for your help.
--
-- rouilj
John Rouillard System Administrator
Renesys Corporation 603-244-9084 (cell) 603-643-9300 x 111
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscript
ty) tables, from which
> partitions inherited. And this restore runs fine.
I realise this may be a silly question (especially for windows), but
the fseek complaint has me wondering.
Are you running a pipleine reatore? E.G:
type dumpfile | pg_restore -j 2
or are you running:
pg_restore -j 2
where the first one was
running for 6 or so hours. The restore worked perfectly. Now if you
have a multi TB db YMMV.
An alternative is to do a PITR image backup. So tell postgres to start
archiving wal logs as part of PIRT, backup the database cluster, tell
postgres the backup is done, copy the
issues if that was happening.
The following may be safer if you are using a shell with noclobber, or
it may not be. Depends on the race conditions in how the shell
implements the noclobber code.
'sh -c "set -o noclobber; cat %p > /var/bak/pgsql/%f"'
--
tovacuum wasn't completed
should make it more likely to be scheduled, before things start
bloating.
If this reschedule period is correct operation, what should I set my
thresholds to:
3 cancelled autovacuums/week?
6 cancelled/2 weeks?
or something else.
Thanks.
--
nes)?
Just for reference I use:
'%t %u@%d(%p): '
--
-- rouilj
John Rouillard System Administrator
Renesys Corporation 603-244-9084 (cell) 603-643-9300 x 111
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
On Wed, Feb 27, 2013 at 05:52:49AM -0500, Charles Sprickman wrote:
> On Feb 25, 2013, at 9:59 AM, John Rouillard wrote:
> > On Sat, Feb 23, 2013 at 12:55:07AM -0500, Charles Sprickman wrote:
> >> [...]
> >> The one huge downside to this is that the logs are so noisy, i
