Re: [PATCH] Support for pg_stat_archiver view

From: Gabriele Bartolini <gabriele(dot)bartolini(at)2ndQuadrant(dot)it>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Fabrizio Mello <fabriziomello(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Support for pg_stat_archiver view
Date: 2014-01-07 20:17:54
Message-ID: 52CC60F2.3020007@2ndQuadrant.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Michael,

Il 07/01/14 09:33, Michael Paquier ha scritto:
> I just had a quick look at v2, and it looks that the patch is in good
> shape.
Thanks.
> Sorry to be picky, but I am not sure that using the character m_type
> is adapted when delivering messages to pgstat facility. You might want
> to use a boolean instead...
I had had the same doubt, and opted for a more generic approach using a
char. I have followed your tip and made the field a boolean.
> MAX_XFN_CHARS is not adapted as well IMO: you should remove it and use
> instead MAXFNAMELEN of xlog_internal.h
Again, I had some concerns about redefining a constant (as MAX_XFN_CHARS
was defined only in pgarch.c). I wonder now if we should change this
behaviour too in pgarch.c (but that's a different patch).

Please find attached version 3.

I will update the commitfest page and add your previous message as
comment/review. I will tentatively add you as reviewer of the patch (as
well as Magnus).

Thanks,
Gabriele

--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele(dot)bartolini(at)2ndQuadrant(dot)it | www.2ndQuadrant.it

Attachment Content-Type Size
pg_stat_archiver.patch.v3 text/plain 23.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message AK 2014-01-07 20:39:22 Re: How to reproduce serialization failure for a read only transaction.
Previous Message Heikki Linnakangas 2014-01-07 19:55:44 Re: cleanup in code