| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_retainxlog for inclusion in 9.3? |
| Date: | 2013-01-03 17:30:39 |
| Message-ID: | CA+TgmobOfoDYhRvvTL5_2FnftauJo6tbC7dV_JwqiJyc2Vg8fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 3, 2013 at 11:32 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Any particular reason? It goes pretty tightly together with
> pg_receivexlog, which is why I'd prefer putting it alongside that one.
> But if you have a good argument against it, I can change my mind :)
Mostly that it seems like a hack, and I suspect we may come up with a
better way to do this in the future.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-01-03 17:47:40 | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |
| Previous Message | Charles Gomes | 2013-01-03 17:28:53 | Re: Writing Trigger Functions in C |