On 2017-05-01 11:31:53 -0700, Peter Geoghegan wrote: > On Mon, May 1, 2017 at 11:24 AM, Andres Freund <and...@anarazel.de> wrote: > > Doing catalog changes in recovery is frought with problems. Essentially > > requires starting one worker per database, before allowing access. > > Do you think it's worth just covering the case where you get an error, > such as a duplicate violation? I imagine that that's the much more > common case.
What exactly are you proposing to do? You mean catching errors in the creating backend, if it didn't crash? That doesn't strike me as a good idea, because it'll push down the likelihood of the issue below where people will see it, but it'll still be likely enough for it to create problems. - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
