Re: review: psql: edit function, show function commands patch
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Jan Urbański <wulczer@wulczer.org>, Postgres - Hackers <pgsql-hackers@postgresql.org>
Date: 2010-08-01T18:43:29Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Sun, Aug 1, 2010 at 11:35 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Personally, rather than sweat about what the exact definition of line >> numbers is, I think we should be moving further in the direction of >> being able to regurgitate source text to identify error locations. > I basically agree with that; but on the other hand, in a large > PL/pgsql function, you may have very similar-looking text in multiple > places. So line numbers are good, too: but then you weren't proposing > to remove those, I assume, just to augment them with additional > information. Right. I'm just suggesting that source text is better than line numbers for exact position identification, so I don't see a lot of value in preserving historical behaviors that change line numbers by one count one way or another. If some of the PLs used zero-based instead of one-based line numbers, we'd be looking to standardize that not cater to their individual idiosyncrasies. regards, tom lane