Re: WAIT FOR NO_THROW option could use some documentation

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>, Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Cc: Kiran Kaki <itskkpg(at)gmail(dot)com>, Rithvika Devisetti <devisettirithvika(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAIT FOR NO_THROW option could use some documentation
Date: 2026-09-03 20:39:35
Message-ID: af5a24c2-230d-4c2c-b82b-324ac14fbf82@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03.09.26 17:21, SATYANARAYANA NARLAPURAM wrote:
> Maybe something along these lines - "NO_THROW option safely prevents the
> database
> from aborting an active transaction, allowing subsequent queries within
> the transaction
> to proceed without losing prior work"?

Maybe that's what it is meant for, but that seems separate from the
status reporting mechanism. It could also send an error message to the
client but not abort the transaction on the server.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-09-03 20:53:38 Re: PGQ catalog representation and pg_dump support
Previous Message Jonathan S. Katz 2026-09-03 20:30:39 PostgreSQL 19 Beta 4 release date