Peter Eisentraut wrote: > On lör, 2010-01-23 at 12:42 -0500, Tom Lane wrote: >> Peter Eisentraut <pete...@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.
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. > The scenario that I encountered is that you go around manually cleaning > them up when the XA software fails for some reason. Hmm, that's a good point though. Maybe it would make sense to add tab completion for ROLLBACK/COMMIT PREPARED, but not for PREPARE TRANSACTION? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
