Skip site navigation (1) Skip section navigation (2)

Re: SQLCODE==-209

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: John Summerfield <pgtest(at)os2(dot)ami(dot)com(dot)au>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: SQLCODE==-209
Date: 2001-10-11 20:25:27
Message-ID: 200110112025.f9BKPRW09083@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
I have added documentation for code 209.  Looks like there are other
undocumented ones.  Should we document them all?

> John Summerfield writes:
> 
> > I'm using 7.2devel from CVS, and as I've already reported, the documentation doesn't build.
> 
> http://www.ca.postgresql.org/devel-corner/docs/postgres/index.html
> 
> > Consequently I'm forced to rely on documentation for 7.1.2/3 which
> > does not mention -209, at least in the ecpg documentation I'm looking
> > at,
> 
> 7.2 doesn't document it either...
> 
> -- 
> Peter Eisentraut   peter_e(at)gmx(dot)net   http://funkturm.homeip.net/~peter
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2001-10-11 20:38:37
Subject: Re: Server crash caused by CHECK on child
Previous:From: OrionDate: 2001-10-11 19:39:38
Subject: Cant get planner to use index (7.1.3-1PGDG)

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-10-11 20:34:10
Subject: Re: postgresql-7.1.3 pg_ctl password authentication and startup
Previous:From: Joe ConwayDate: 2001-10-11 06:19:39
Subject: Re: Efficient slicing/substring of TOAST values (for comment)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group