| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-16 18:38:21 |
| Message-ID: | 54E2391D.4010500@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/16/15 2:41 AM, Andres Freund wrote:
> Since you actually don't want cancellations for the long running
> reporting queries it very much might be sensible to switch to a more
> complicated version of HeapTupleSatisfiesVacuum() if there's longrunning
> queries. One that can recognize if rows are actually visible to any
> backend, or if there are just snapshots that see older rows. I've
> previously wondered how hard this would be, but I don't think it's
> *that* hard. And it'd be a much more general solution.
Josh Berkus mentioned on IRC that they're working on improving vacuum,
and I think it was something along these lines.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-02-16 20:51:22 | Expanding the use of FLEXIBLE_ARRAY_MEMBER for declarations like foo[1] |
| Previous Message | Eric Grinstein | 2015-02-16 17:00:45 | Re: [HACKERS] GSoC 2015 - mentors, students and admins. |