pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Markus Wagner <wagner@imsd.uni-mainz.de>
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: Re: SPI_exec does not return!
Date: Wed, 18 Jul 2001 06:54:34 -0400 (EDT)
Message-ID: <200107181054.f6IAsYd20969@jupiter.us.greatbridge.com> (raw)
In-Reply-To: <3B55445B.36E16A4@imsd.uni-mainz.de>

Markus Wagner wrote:
> Hi,
>
> if I do a SELECT on a non-existing table, SPI_exec won't return.
> I get, e. g. in pgaccess, an error message "<table> does not exist",
> and my code below the function call is never reached.

    Right,  the  SPI_exec()  call  in  turn  calls the PostgreSQL
    parser and that raises an elog(ERROR) which longjmp()'s  back
    into  the  backends  main  loop  waiting  for the next client
    query.

>
> So why return error codes for SPI_exec when you cannot evaluate them?

    What do you want here? No error,  just  an  empty  result  of
    unspecified  format?   If the parser cannot determine (due to
    nonexistance of a table) which datatype the  columns  of  the
    result  set  at least should have, what else could he do than
    trowing an ERROR?

>
> The background:
>
> I need to distinguish different client connections within a trigger
> function.
> To do this, I create a temporary table within a "login" function.
> My trigger must check for the existence of this function.
> I cannot think of any other method, since there is no "connection id" or
> something like that!

    Unfortunately PL/pgSQL doesn't have global variables.  PL/Tcl
    can  have.   If you cannot code a part of the login mechanism
    in PL/Tcl, setting a global variable and  returning  that  in
    another  PL/Tcl  function, you could create a temp table with
    the same name in every connection and fill the  connection-ID
    into that.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (2+ messages)

Message-ID: <200107181054.f6IAsYd20969@jupiter.us.greatbridge.com>
Permalink:  ../200107181054.f6IAsYd20969@jupiter.us.greatbridge.com/
Also on:    postgresql.org/message-id/200107181054.f6IAsYd20969@jupiter.us.greatbridge.com

 · 

reply

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: JanWieck@Yahoo.com, wagner@imsd.uni-mainz.de
  Subject: Re: SPI_exec does not return!
  In-Reply-To: <200107181054.f6IAsYd20969@jupiter.us.greatbridge.com>

* 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