From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | jimshaw(at)iinet(dot)net(dot)au |
Subject: | prepared transactions improvements |
Date: | 2018-02-20 22:18:43 |
Message-ID: | 151916512323.3883.11171138545790546098@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.3/static/sql-prepare-transaction.html
Description:
Under PREPARE TRANSACTION it says that transaction_id must be unique, it
doesn't say what happens when it is not unique.
It might be useful to add a note mentioning max_prepared_transactions needs
to be configured before prepared transactions are enabled, although there's
already a note saying to leave it at 0 if prepared transactions are not
required.
Under COMMIT PREPARED and ROLLBACK PREPARED it should also say what happens
if transaction_id does not exist.
Thanks,
Jim
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2018-02-21 13:32:38 | Pltcl install |
Previous Message | PG Doc comments form | 2018-02-20 17:37:28 | Support Inquiry |