| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: preserving forensic information when we freeze |
| Date: | 2013-12-23 00:57:44 |
| Message-ID: | CA+Tgmob0hZWa1gi+s3Zho3r_mFabcwshoL8HswNCg-hw-YE7GQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 20, 2013 at 8:01 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2013-12-20 07:58:46 -0500, Robert Haas wrote:
>> I think the immediate problem is to decide whether this patch ought to
>> make the xmin column display the result of GetXmin() or GetRawXmin().
>> Thoughts on that?
>
> I slightly favor GetRawXmin().
Committed that way for now. It seems more consistent with what we do
elsewhere. We neglected to write documentation for this change, so
here's a patch for that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| new-freeze-doc.patch | text/x-patch | 7.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-12-23 01:45:02 | Re: CLUSTER FREEZE |
| Previous Message | Peter Geoghegan | 2013-12-22 23:42:18 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |