From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
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 19:56:19 |
Message-ID: | 4B5CA5E3.7020908@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Heikki Linnakangas wrote:
>> Bruce Momjian wrote:
>>> Heikki Linnakangas wrote:
>>>> 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.
>> Hmm, I thought we explained that in the manual, but I can't see it. I
>> think we should add a note to the ref page of PREPARE TRANSACTION,
>> something like:
>>
>> "PREPARE TRANSACTION is not intended for use in applications or in
>> interactive sessions. It's purpose is to allow an external transaction
>> manager to perform atomic global transactions across multiple databases
>> or other transactional resources. Unless you're writing a transaction
>> manager, you probably shouldn't be using PREPARE TRANSACTION"
>
> I was thinking of adding something in the psql C source code to explain
> why certain commands are not implemented for tab completion.
Yeah, that's a good idea too.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-01-24 20:32:53 | default_language |
Previous Message | Baron Schwartz | 2010-01-24 19:54:33 | Re: MySQL-ism help patch for psql |