genbki stricter error handling - Mailing list pgsql-hackers

From Peter Eisentraut
Subject genbki stricter error handling
Date
Msg-id ca8ee41d-241b-1bf3-71f0-aaf1add6d3c5@enterprisedb.com
Whole thread Raw
Responses Re: genbki stricter error handling
List pgsql-hackers
genbki.pl says:

# Perform OID lookups on an array of OID names.
# If we don't have a unique value to substitute, warn and
# leave the entry unchanged.
# (A warning seems sufficient because the bootstrap backend will reject
# non-numeric values anyway.  So we might as well detect multiple problems
  # within this genbki.pl run.)

This is fine, but I have found this to be a bit cumbersome in practice 
sometimes, because errors are then not easily seen at build time but 
have to be extracted from some log files during test runs.

I propose the attached patch to make genbki.pl error out if it 
encounters any errors in this routine, while preserving the property 
that all errors in one run are reported.

Attachment

pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Deadlock risk while inserting directly into partition?
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench logging broken by time logic changes