| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Rui DeSousa <rui(at)crazybean(dot)net> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow "snapshot too old" error, to prevent bloat |
| Date: | 2015-03-16 15:46:43 |
| Message-ID: | CA+TgmoaG4CVXp7nbsVqm16ZvVFw5au9L2QvOQjRcrd7Fm10XvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Mar 15, 2015 at 8:04 PM, Rui DeSousa <rui(at)crazybean(dot)net> wrote:
> Would a parameter to auto terminate long running transactions be a better solution? Terminating the long running transaction would allow for the normal vacuuming process to cleanup the deleted records thus avoiding database bloat without introducing new semantics to Postgres's MVCC. I would also recommend that the default be disabled.
An advantage of Kevin's approach is that you don't have to abort *all*
long-running transactions, only those that touch data which has been
modified since then. If your system is read-mostly, that could
dramatically reduce the number of aborts.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-03-16 15:50:13 | Re: get_object_address support for additional object types |
| Previous Message | Stephen Frost | 2015-03-16 15:26:02 | Re: get_object_address support for additional object types |