| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Detrimental performance impact of ringbuffers on performance |
| Date: | 2016-04-13 15:27:48 |
| Message-ID: | 20160413152748.ufkqzkk3slmtcddo@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-04-13 06:57:15 -0400, Robert Haas wrote:
> You will eventually, because each scan will pick a new ring buffer,
> and gradually more and more of the relation will get cached. But it
> can take a while.
You really don't need much new data to make that an unobtainable goal
... :/
> I'd be more inclined to try to fix this by prewarming the buffers that
> were in shared_buffers at shutdown.
That doesn't solve the problem of not reacting to actual new data? It's
not that uncommon to regularly load new data with copy and drop old
partitions, just to keep the workload memory resident...
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-04-13 15:30:32 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Previous Message | Robert Haas | 2016-04-13 15:27:09 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |