Re: tab completion for prepared transactions?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: tab completion for prepared transactions?
Date: 2010-01-23 17:42:40
Message-ID: 10625.1264268560@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ivan Sergio Borgonovo 2010-01-23 17:53:30 Re: Re: Cstring vs. Datum values ( BuildTupleFromCStrings vs. BlessTupleDesc)
Previous Message Greg Stark 2010-01-23 17:35:28 Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.