Re: adding a new column in IDENTIFY_SYSTEM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: adding a new column in IDENTIFY_SYSTEM
Date: 2011-05-05 15:59:21
Message-ID: 4907.1304611161@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> So even if people don't believe in the rationale behind the patch,
>> would allowing it harm anything at this point?

> Adding it for the sake of upgrades seems very far fetched.

> Adding it for the sake of giving a better error message seems like a
> very good idea. But in that case, the client side code to actually
> give a better error message should be included from the start, IMHO.

What's not apparent to me is how we'll even get to this check; if
there's a mismatch, won't the database system identifier comparison
fail first in most scenarios?

I'm also wondering why send WAL version number and not, say, catalog
version number, if there's some idea that we need more tests than the
system identifier comparison.

Given reasonable answers to these questions, I'd not object to putting
in additional error testing. I concur with Magnus that the patch should
actually provide those tests, and not just put in an unused field.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-05-05 16:25:09 Re: characters or bytes?
Previous Message Magnus Hagander 2011-05-05 15:54:01 Re: adding a new column in IDENTIFY_SYSTEM