| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tab completion for prepared transactions? |
| Date: | 2010-01-24 19:45:15 |
| Message-ID: | 4B5CA34B.504@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> 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?
>
> Huh? PREPARE TRANSACTION creates a new gxid, so there's nothing for it
> to complete against.
Well, you could still complete "PREPARE TR" to "PREPARE TRANSACTION",
but I agree it's not very useful. But I was arguing for not having
tab-completion for PREPARE TRANSACTION, so the point is moot anyway.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-01-24 19:52:55 | Re: tab completion for prepared transactions? |
| Previous Message | Andrew Dunstan | 2010-01-24 19:45:10 | Re: 8.5 vs. 9.0, Postgres vs. PostgreSQL |