| From: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
|---|---|
| To: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Running pg_dump from a slave server |
| Date: | 2016-08-17 03:50:36 |
| Message-ID: | CAJNY3iusgtWuxTTxwQ1VUp=vuDCV5xWZmbDQgBB5PwHjai0ZGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
>
>
> But do you have statements which causes Exclusive Locks? Ignoring them in
> OLTP won't make your life any easier.
>
> (Keeping avoiding to get into 'recovery conflict' as your sole goal) If
> you decide to run pg_dump from master, it would block such statements
> which have Exclusive locking. This would cause delays, deadlocks, livelocks
> etc and it might take a while for your before you can figure out what is
> going on.
>
> I would say try to find out who is and why is someone creating Exclusive
> locks.
>
Yeah! The pg_dump was already running on the master... it's been running
for months.. I just wanted to change now to use the slave, but it seems I
can't right?
Exclusive locking - I probably have statements that causes this. Is there
any way I could "track" them?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkata B Nagothi | 2016-08-17 04:00:47 | Re: Running pg_dump from a slave server |
| Previous Message | Sameer Kumar | 2016-08-17 03:43:00 | Re: Running pg_dump from a slave server |