| From: | Amit kapila <amit(dot)kapila(at)huawei(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Patch to compute Max LSN of Data Pages |
| Date: | 2012-11-16 11:22:14 |
| Message-ID: | 6C0B27F7206C9E4CA54AE035729E9C3828549DBD@szxeml509-mbx |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday, November 15, 2012 7:30 PM Robert Haas wrote:
On Thu, Nov 15, 2012 at 12:08 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
>> Okay.
>> So as Robert and Alvaro suggested to have it separate utility rather than
>> having options in pg_resetxlog to print MAX LSN seems to be quite
>> appropriate.
>> I am planning to update the patch to make it a separate utility as
>> pg_computemaxlsn with options same as what I have proposed for pg_resetxlog
>> to print MAX LSN.
>> So considering it a separate utility there can be 2 options:
>> a. have a utility in contrib.
>> b. have a utility in bin similar to pg_resetxlog
> I guess I'd vote for contrib, but I wouldn't be crushed if it went the
> other way.
Updated test cases and patch to have separate utility in contrib for pg_computemaxlsn are attached with this mail.
With Regards,
Amit Kapila.
| Attachment | Content-Type | Size |
|---|---|---|
| pg_computemaxlsn.patch | application/octet-stream | 18.0 KB |
| Test_find_max_lsn_from_datafiles.txt | text/plain | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-11-16 11:40:03 | Re: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown |
| Previous Message | Kohei KaiGai | 2012-11-16 11:01:20 | Re: [v9.3] Extra Daemons (Re: elegant and effective way for running jobs inside a database) |