Re: tab completion for prepared transactions? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tab completion for prepared transactions?
Date
Msg-id 10625.1264268560@sss.pgh.pa.us
Whole thread Raw
In response to tab completion for prepared transactions?  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: tab completion for prepared transactions?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Was there a designed-in reason not to have psql tab completion for
> COMMIT/ROLLBACK PREPARED ...?  It does complete the "PREPARED" but not
> the transaction identifiers.  Maybe it's not a common use case, but
> these transaction identifiers sure can be nontrivial to type.

Hmm, what's the use scenario?  I would think that painfully long
gxids would come from some XA manager software, which would be
responsible for committing or canceling them.  Manual override
of that would usually be a bad idea.

In short, there's probably no "designed-in reason", but it's not
clear to me that it's worth the code & maintenance effort to have
tab completion for that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.
Next
From: Ivan Sergio Borgonovo
Date:
Subject: Re: Re: Cstring vs. Datum values ( BuildTupleFromCStrings vs. BlessTupleDesc)