Re: [HACKERS] psql variables fixed (?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] psql variables fixed (?)
Date: 2000-01-15 05:54:11
Message-ID: 2180.947915651@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> I'd be a little reluctant to give up the alternate "::" syntax, only
> because I'm not sure I trust the standards folks to not stomp on the
> alternative at some point in the future.

Even more to the point, we now have a substantial pool of user
applications that rely on "::" (I know a lot of my company's
code does, for example). We can't just blow off those users.

Peter's current proposal seems OK to me, with the caveat that we
will have to be *very* circumspect about introducing additional
variables-automatically-defined-by-psql in the future. Every
time we do, we risk breaking existing user scripts, not unlike
what happens when we introduce a new reserved word in the backend
grammar.

Lane's Other Law: the price of success is backwards compatibility.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-15 06:12:59 Standards (was Re: psql variables fixed (?))
Previous Message Tatsuo Ishii 2000-01-15 05:52:42 Re: [HACKERS] libpq+MB/putenv(), getenv() clean up