Re: pg_receivexlog and replication slots - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_receivexlog and replication slots
Date
Msg-id CA+TgmoY71F2ZdCDMxq9NDt-wrvHFOgDhYOTfwstL2aqdf9d7EQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_receivexlog and replication slots  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_receivexlog and replication slots  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Sun, Aug 31, 2014 at 9:45 AM, Magnus Hagander <magnus@hagander.net> wrote:
> Do we really want those Asserts? There is not a single Assert in
> bin/pg_basebackup today - as is the case for most things in bin/. We
> typically use regular if statements for things that "can happen", and
> just ignore the others I think - since the callers are fairly simple
> to trace.

I have no opinion on whether we want these particular Assert() calls,
but I note that using Assert() in front-end code only became possible
in February of 2013, as a result of commit
e1d25de35a2b1f809e8f8d7b182ce0af004f3ec9.  So the lack of assertions
there may not be so much because people thought it was a bad idea as
that it didn't use to work.  Generally, I favor the use of Assert() in
front-end code in the same scenarios in which we use it in back-end
code: for checks that shouldn't burden production builds but are
useful during development.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: RLS Design
Next
From: Andres Freund
Date:
Subject: Re: Inverse of pg_get_serial_sequence?