| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sanjay Patil <sanjaypatilwork(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PGRES_EMPTY_QUERY from Postgre 14.3 |
| Date: | 2023-08-21 15:52:34 |
| Message-ID: | CAKFQuwYG4OQH9ESsst4ZrBEHaDyDbuXSAHVu=yYod9683nb+6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Aug 21, 2023 at 8:18 AM Sanjay Patil <sanjaypatilwork(at)gmail(dot)com>
wrote:
> Hi Team
>
> Currently, we are facing PGRES_EMPTY_QUERY return from Postgres DB on 14.3
> version.
>
> Its not every case, Whenever load increase to DB. Could you please suggest
> us.
>
>
I get that a volume-based error is harder to reproduce but at least try and
provide some details like schema, query, and environment, when asking for
others to debug your system.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-08-21 16:04:14 | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
| Previous Message | Euler Taveira | 2023-08-21 15:23:55 | Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory |