From: | prasanna rk <prasanna2mail(at)gmail(dot)com> |
---|---|
To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Commit not required for update statement |
Date: | 2018-10-15 05:06:35 |
Message-ID: | CADzxCad1qK4b520-c+5EHcM7O0+zktuDK0PKfZkUVD7Pgz3yVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Mark
Thank you for sharing, as per the link
https://www.postgresql.org/docs/current/static/tutorial-transactions.html
"PostgreSQL actually treats every SQL statement as being executed within a
transaction. If you do not issue a BEGINcommand, then each individual
statement has an implicit BEGIN and (if successful) COMMIT wrapped around
it. A group of statements surrounded by BEGIN and COMMIT is sometimes
called a *transaction block*."
Note
Some client libraries issue BEGINand COMMIT commands automatically, so that
you might get the effect of transaction blocks without asking. Check the
documentation for the interface you are using.
Does this mean..every statement which does not have begin will be
automatically commited.
On Mon, 15 Oct 2018, 09:20 Mark Kirkwood, <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
wrote:
> Hi,
>
> Definitely worth reading what the docs say about this, should clear
> things up:
> https://www.postgresql.org/docs/current/static/tutorial-transactions.html
>
> regards
>
> Mark
>
>
> On 15/10/18 15:30, prasanna rk wrote:
> > Hi all
> >
> > We are running posters 10.4 version, wanted to know if commit
> > statement is not required for update.
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | soumitra bhandary | 2018-10-15 05:48:53 | Re: Null value returned by function pg_last_wal_receive_lsn() inLogical Replication |
Previous Message | Mark Kirkwood | 2018-10-15 03:49:38 | Re: Commit not required for update statement |