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

From Tom Lane
Subject Re: savepoint name vs prepared transaction name
Date
Msg-id 6149.1255703932@sss.pgh.pa.us
Whole thread Raw
In response to savepoint name vs prepared transaction name  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Responses Re: savepoint name vs prepared transaction name
List pgsql-general
=?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= <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.

            regards, tom lane

pgsql-general by date:

Previous
From: Arnaud Lesauvage
Date:
Subject: Re: pgsql2shp : Encoding headache
Next
From: Tom Lane
Date:
Subject: Re: Wrong estimation of rows for hash join