On Sunday, September 19, 2021, Anthony Berglas wrote:
>
> I note that nothing has happened.
>
> In future I would suggest that you simply tell people that document
> updates are not really welcome. Otherwise you waste people's time.
>
That isn’t generally true, and as I am not an Oracle my abili
On Thu, Jul 29, 2021 at 8:04 AM PG Doc comments form
wrote:
> For all this documentation, it is completely unclear how to handle the most
> common, simple case. I.e.
>
> Select balance into :bal ...where key =123;
> Update set balance = :bal+100 where key = 100
I don't think that that's the mos
Hello David,
I note that nothing has happened.
In future I would suggest that you simply tell people that document updates
are not really welcome. Otherwise you waste people's time.
The locking issue is actually quite serious.
Cheers,
Anthony
On Tue, Aug 3, 2021 at 10:01 AM Anthony Berglas
Hello David,
Thanks for that, I had thought that you were a committer. Sounds like it
might all be a bit too difficult.
Anthony
On Tue, Aug 3, 2021 at 9:39 AM David G. Johnston
wrote:
> On Mon, Aug 2, 2021 at 4:30 PM Anthony Berglas
> wrote:
>
>> You are talking about optimistic locking, com
Hello David,
You are talking about optimistic locking, commonly used for web
applications where there is no transaction kept open during user think
time. A COMMIT between the SELECT and the UPDATE.
This is also what was needed for traditional MySql running only in
AutoCommit mode. It requires n
On Mon, Aug 2, 2021 at 4:30 PM Anthony Berglas wrote:
> You are talking about optimistic locking, commonly used for web
> applications where there is no transaction kept open during user think time.
>
Yes, I said as much a couple of emails ago.
> And more importantly it is very important that
On Sun, Aug 1, 2021 at 11:35 PM Anthony Berglas wrote:
> I have attached a proposed doc update that makes the problem clearer. I
> think that this is important because if people do not understand it they
> will write buggy code and then blame Postgresql for losing updates, which
> is totally una
Hello David,
I have attached a proposed doc update that makes the problem clearer. I
think that this is important because if people do not understand it they
will write buggy code and then blame Postgresql for losing updates, which
is totally unacceptable. So please do action this. I have teste
OK, I'll put something for you to review. Most programmers simply ignore
locking and wonder why it sometimes goes wrong.
On Fri, Jul 30, 2021 at 2:22 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thu, Jul 29, 2021 at 8:44 PM Anthony Berglas
> wrote:
>
>> My point is that while
My point is that while I can follow the academic style discussion, most of
my colleagues could not. They just need to have a clear idea of how to
handle the common case, which is to use a database using some programming
language.
Early on, for Read Committed, it should discuss and ideally provide
On Thu, Jul 29, 2021 at 8:44 PM Anthony Berglas wrote:
> My point is that while I can follow the academic style discussion, most of
> my colleagues could not. They just need to have a clear idea of how to
> handle the common case, which is to use a database using some programming
> language.
>
On Thu, Jul 29, 2021 at 8:04 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/transaction-iso.html
> Description:
>
> For all this documentation, it is completely unclear how to handle the most
> comm
On Wed, Jul 28, 2021 at 03:48:04AM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/transaction-iso.html
> Description:
>
> For all this documentation, it is completely unclear how to handle the m
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/transaction-iso.html
Description:
For all this documentation, it is completely unclear how to handle the most
common, simple case. I.e.
Select balance into :bal ...where key =123;
Updat
14 matches
Mail list logo