From: Tom Lane <tgl@sss.pgh.pa.us>
To: Erik Wasser <erik.wasser@iquer.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Can SELECT statements throw an error
Date: Thu, 21 Jul 2005 10:35:26 -0400
Message-ID: <19902.1121956526@sss.pgh.pa.us> (raw)
In-Reply-To: <200507211620.37120.erik.wasser@iquer.net>
References: <200507211620.37120.erik.wasser@iquer.net>
Erik Wasser <erik.wasser@iquer.net> writes:
> can SELECT statements throw errors except the followings:
> - SQL syntax errors
> - connection based errors (database is down/etc...)
> - deadlocks
> Did I miss an option?
Many. Consider
select 1 / 0
In general I'd think that most errors in the "data exception",
"cardinality violation", "insufficient resources",
and "operator intervention" categories are possible. See the
error codes appendix for some ideas.
And of course, if the SELECT invokes a user-defined function,
no holds are barred ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, erik.wasser@iquer.net
Subject: Re: Can SELECT statements throw an error
In-Reply-To: <19902.1121956526@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox