[PATCH] Teach Catalog.pm how many attributes there should be per DATA() line

From: David Christensen <david(at)endpoint(dot)com>
To: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: [PATCH] Teach Catalog.pm how many attributes there should be per DATA() line
Date: 2015-10-06 13:15:57
Message-ID: 5BC2FB61-2B35-470D-9B3C-429876C41406@endpoint.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fixes a build issue I ran into while adding some columns to system tables:

Throws a build error if we encounter a different number of fields in a
DATA() line than we expect for the catalog in question.

Previously, it was possible to silently ignore any mismatches at build
time which could result in symbol undefined errors at link time. Now
we stop and identify the infringing line as soon as we encounter it,
which greatly speeds up the debugging process.

Attachment Content-Type Size
0001-Teach-Catalog.pm-how-many-attributes-there-should-be.patch application/octet-stream 2.2 KB
unknown_filename text/plain 107 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Christensen 2015-10-06 13:17:02 [PATCH] Comment fixes
Previous Message Nathan Wagner 2015-10-06 13:05:24 bugs and bug tracking