Re: savepoint name vs prepared transaction name - Mailing list pgsql-general

From Grzegorz Jaśkiewicz
Subject Re: savepoint name vs prepared transaction name
Date
Msg-id 2f4958ff0910160757k38126fe4gdc26398c532cad98@mail.gmail.com
Whole thread Raw
In response to Re: savepoint name vs prepared transaction name  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general


2009/10/16 Tom Lane <tgl@sss.pgh.pa.us>
Grzegorz Jaśkiewicz <gryzman@gmail.com> writes:
> Is there any reason, why I can't put quotes around name of savepoint, but I
> have/can do this for prepare transaction ?

Savepoint names are identifiers; the SQL spec says so.  Prepared
transaction GIDs are string literals.  The relevant discussion
about that is here:
http://archives.postgresql.org/pgsql-hackers/2005-05/msg01292.php

We could conceivably allow an identifier too in PREPARE TRANSACTION,
but I think that that might be more dangerous than helpful, because
of the implicit case folding for identifiers.  'XX' and 'xx' are
distinct but XX and xx wouldn't be.  There are a few other places
where we allow strings and identifiers interchangeably, but AFAIR
they are all places where case doesn't matter.

makes sense. Cheers Tom.



--
GJ

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Wrong estimation of rows for hash join
Next
From: InterRob
Date:
Subject: Re: [postgis-users] pgsql2shp : Encoding headache