| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: startup process stuck in recovery |
| Date: | 2017-10-10 01:02:20 |
| Message-ID: | CAH2-Wzk66CmAuDiNrosByNX8+mR0-ca92OC=vxb4ntfUwdJ17g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Oct 9, 2017 at 5:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> and did not see any untoward behavior, at least not till I got to enough
> temp tables to overrun the master's shared lock table, and even then it
> cleaned up fine. At no point was the standby process consuming anywhere
> near as much CPU as the master's backend.
>
> What am I missing to reproduce the problem?
Just a guess, but do you disable autovacuum on your dev machine? (I know I do.)
It's possible that this is relevant:
https://postgr.es/m/CAB-EU3RawZx8-OzMfvswFf6z+Y7GOZf03TZ=bez+PbQX+A4M7Q@mail.gmail.com
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-10 01:05:18 | Re: startup process stuck in recovery |
| Previous Message | Tom Lane | 2017-10-10 00:30:32 | Re: startup process stuck in recovery |