| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(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 |
| Subject: | Re: [PATCH] Patch to compute Max LSN of Data Pages |
| Date: | 2012-11-15 14:00:09 |
| Message-ID: | CA+TgmobHz=vqptoRPb5Lx6x7PDXVjc4MQTJ+Qrve2Q7Km953qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-11-15 14:22:56 | Re: [PATCH 02/14] Add support for a generic wal reading facility dubbed XLogReader |
| Previous Message | Amit kapila | 2012-11-15 13:59:12 | Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown |