Re: non-exclusive backup cleanup is mildly broken - Mailing list pgsql-hackers

From Tom Lane
Subject Re: non-exclusive backup cleanup is mildly broken
Date
Msg-id 7602.1576605913@sss.pgh.pa.us
Whole thread Raw
In response to Re: non-exclusive backup cleanup is mildly broken  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: non-exclusive backup cleanup is mildly broken  (Magnus Hagander <magnus@hagander.net>)
Re: non-exclusive backup cleanup is mildly broken  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> Perhaps I spoke too soon: I'm not sure whether Michael's comments
> amount to an objection. While I give him a chance to respond, here's
> an updated patch.

Took a quick look.  I agree that this seems a lot cleaner than the
alternative proposals.  I'd suggest however that the header comment
for do_pg_abort_backup could do with more work, perhaps along the
lines of "The odd-looking signature allows this to be registered
directly as a shmem_exit handler".

Personally I'd have kept the handler as a separate function that's just
a one-line wrapper around "void do_pg_abort_backup(bool emit_warning)".
We don't usually treat callbacks as functions to be also called in
their own right.  But if you don't want to do that, I'll settle for an
acknowledgement of the hack in the comment.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: non-exclusive backup cleanup is mildly broken
Next
From: Mahendra Singh
Date:
Subject: Re: RFC: split OBJS lines to one object per line