| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow "snapshot too old" error, to prevent bloat |
| Date: | 2015-02-23 00:35:28 |
| Message-ID: | 54EA75D0.9090402@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/22/2015 11:48 AM, Kevin Grittner wrote:
>
> (2) Use a course enough granularity on time and a short enough
> maximum for the GUC to just keep a circular buffer of the mappings
> in memory. We might be able to make this dense enough that one
> minute resolution for up to 60 days could fit in 338kB. Obviously
> that could be reduced with courser granularity or a shorter
> maximum.
>
This doesn't sound too bad to me. Presumably these would be tunable. I
think one minute granularity would be fine for most purposes, but I can
imagine people who would want it finer, like 10 seconds, say.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-02-23 00:39:37 | Re: pg_check_dir comments and implementation mismatch |
| Previous Message | Tomas Vondra | 2015-02-23 00:34:12 | Re: TABLESAMPLE patch |