| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | "Bandi, Venkataramana - Dell Team" <Venkataramana(dot)Bandi(at)dellteam(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "Kishore, Nanda - Dell Team" <Nanda(dot)Kishore(at)dellteam(dot)com>, "Alampalli, Kishore" <Kishoreravishankar(dot)Alampalli(at)dellteam(dot)com> |
| Subject: | Re: Query on Postgres SQL transaction |
| Date: | 2024-03-15 18:36:44 |
| Message-ID: | CAKAnmmJcMTxoD2ao8z8YXiU-9FspXZc9L+VKGrAYuig8mN3XSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
That's a very vague question, but you can trace exactly what is happening
by issuing
SET log_statement = 'all';
Ideally at the session level by your application, but can also set it at
the database and user level. If all else fails, set it globally (i.e.
postgresql.conf). Turn it off again as soon as possible, it will make your
logs extremely verbose. But you can track exactly what your application is
doing.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PetSerAl | 2024-03-16 11:14:27 | Single-User Mode oid assignment |
| Previous Message | Adrian Klaver | 2024-03-15 18:05:05 | Re: PostGres ODBC too slow |