From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tab completion for prepared transactions? |
Date: | 2010-01-24 17:32:07 |
Message-ID: | 201001241732.o0OHW7L02341@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
> Peter Eisentraut wrote:
> > On l?r, 2010-01-23 at 12:42 -0500, Tom Lane wrote:
> >> 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.
>
> Right, I vaguely recall that the idea of tab-completion for those
> commands was rejected when 2PC was added because of that. A user sitting
> at a psql terminal is not supposed to prepare a transaction. That's
> application server's business.
I think we should add a C comment documenting that fact.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-01-24 17:35:38 | Re: Largeobject Access Controls (r2460) |
Previous Message | Tom Lane | 2010-01-24 17:30:26 | Re: further explain changes |