public inbox for [email protected]help / color / mirror / Atom feed
Docs about INSERT wait in Read Commited transaction 3+ messages / 3 participants [nested] [flat]
* Docs about INSERT wait in Read Commited transaction @ 2022-05-07 22:12 PG Doc comments form <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: PG Doc comments form @ 2022-05-07 22:12 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/transaction-iso.html Description: Hello I've noticed, if two transactions in read committed mode are trying to insert same value to unique column, second transaction INSERT will wait for the first transaction commit or rollback. Can't see this behavior explicitly stated in the doc about transaction isolation modes. Thank you You are doing a great job with PostgreSQL docs! ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Docs about INSERT wait in Read Commited transaction @ 2022-05-09 01:27 David G. Johnston <[email protected]> parent: PG Doc comments form <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: David G. Johnston @ 2022-05-09 01:27 UTC (permalink / raw) To: [email protected] <[email protected]>; [email protected] <[email protected]> On Saturday, May 7, 2022, PG Doc comments form <[email protected]> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/transaction-iso.html > Description: > > Hello > I've noticed, if two transactions in read committed mode are trying to > insert same value to unique column, second transaction INSERT will wait for > the first transaction commit or rollback. Can't see this behavior > explicitly > stated in the doc about transaction isolation modes. > > It is documented elsewhere: https://www.postgresql.org/docs/current/index-unique-checks.html David J. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Docs about INSERT wait in Read Commited transaction @ 2022-05-09 01:36 Ivan Tsyba <[email protected]> parent: David G. Johnston <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Ivan Tsyba @ 2022-05-09 01:36 UTC (permalink / raw) To: David G. Johnston <[email protected]>; +Cc: [email protected] Yes, the behavior is documented there. I would suggest to add one sentence about it to transactions page. Thank you пн, 9 трав. 2022, 04:27 користувач David G. Johnston < [email protected]> пише: > On Saturday, May 7, 2022, PG Doc comments form <[email protected]> > wrote: > >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/14/transaction-iso.html >> Description: >> >> Hello >> I've noticed, if two transactions in read committed mode are trying to >> insert same value to unique column, second transaction INSERT will wait >> for >> the first transaction commit or rollback. Can't see this behavior >> explicitly >> stated in the doc about transaction isolation modes. >> >> > It is documented elsewhere: > > https://www.postgresql.org/docs/current/index-unique-checks.html > > David J. > > ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2022-05-09 01:36 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-05-07 22:12 Docs about INSERT wait in Read Commited transaction PG Doc comments form <[email protected]> 2022-05-09 01:27 ` David G. Johnston <[email protected]> 2022-05-09 01:36 ` Ivan Tsyba <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox