| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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:32:16 |
| Message-ID: | 1264361536.3644.2.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On sön, 2010-01-24 at 19:43 +0200, Heikki Linnakangas wrote:
> "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 have never had a chance to use one of these "transaction managers".
I'm probably using it in a non-orthodox way then. What is the
difference between a transaction manager and an application that opens
multiple connections and does PREPARE + COMMIT PREPARED across them?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-01-24 19:38:28 | Re: commit fests |
| Previous Message | Robert Haas | 2010-01-24 19:30:30 | Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns |