Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 04FEB1EB83EA
	for <pgsql-admin@postgresql.org>; Thu, 23 Feb 2012 16:23:14 -0400 (AST)
Received: from pp-ag1.abag.ca.gov ([198.31.87.11])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <FredP@abag.ca.gov>) id 1S0fC1-00068a-MM
	for pgsql-admin@postgresql.org; Thu, 23 Feb 2012 20:23:12 +0000
Received: from pps.filterd (pp-ag1 [127.0.0.1])
	by pp-ag1.abag.ca.gov (8.14.4/8.14.4) with SMTP id q1NKGbGO025298
	for <pgsql-admin@postgresql.org>; Thu, 23 Feb 2012 12:22:54 -0800
Received: from gwia1.abag.ca.gov ([172.16.1.27])
	by pp-ag1.abag.ca.gov with ESMTP id 135tjmg1kp-1
	for <pgsql-admin@postgresql.org>; Thu, 23 Feb 2012 12:22:54 -0800
Received: from d02-MTA by gwia1.abag.ca.gov
	with Novell_GroupWise; Thu, 23 Feb 2012 12:22:54 -0800
Message-Id: <4F462F9C020000A70001B6C7@gwia1.abag.ca.gov>
X-Mailer: Novell GroupWise Internet Agent 8.0.2 
Date: Thu, 23 Feb 2012 12:22:52 -0800
From: "Fred Parkinson" <FredP@abag.ca.gov>
To: <pgsql-admin@postgresql.org>,
	"Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Subject: Re: Can't query the sequence table of a serial primary
 key.
References: <4F461C53020000A70001B6BB@gwia1.abag.ca.gov>
	<4F4640810200002500045AD6@gw.wicourts.gov>
In-Reply-To: <4F4640810200002500045AD6@gw.wicourts.gov>
Mime-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7498,
 1.0.260,
	0.0.0000
	definitions=2012-02-23_07:2012-02-23, 2012-02-23,
	1970-01-01 signatures=0
X-Pg-Spam-Score: -4.2 (----)
Content-Type: multipart/alternative; boundary="=__PartCDE3C90C.1__="
X-Archive-Number: 201202/97
X-Sequence-Number: 39157

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=__PartCDE3C90C.0__=
Content-Type: multipart/alternative; boundary="=__PartCDE3C90C.1__="

--=__PartCDE3C90C.1__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Thanks everyone for your replies.
=20
In my original post I failed to EXACTLY reproduce the problem, in that =
capital letters were involved which I left out of the description.
For example, the id had been set up as "ID" serial primary key, and the =
sequencer was consequently named 'mytable_ID_seq' not 'mytable_id_seq' (he =
was stabbed to death by details!)
When I ran the select statement I DID reproduce the capital letters as =
they existed, but got the error I described.
=20
In the effort to create a test sample I left out all caps and made =
everything lower case.
=20
Viola! The problem disappeared!  Sanity restored (for now).
=20
That's it, no more caps for me!
=20
Thanks again for everyone's efforts to help.
=20
Fred


>>> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> 02/23/2012 11:34 AM >>>
"Fred Parkinson" <FredP@abag.ca.gov> wrote:

> When I do \d I see the table and the sequencer under 'List of
> relations'.  But when I run select * from mytable_id_seq;
> postgresql responds with: relation 'mytable_id_seq' does not
> exist.

It works for me.  Can you provide a small self-contained test case
which demonstrates the problem?

Hopefully you are aware of these functions, which might be easier:

http://www.postgresql.org/docs/8.4/interactive/functions-sequence.html

-Kevin

--=__PartCDE3C90C.1__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19190"></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Arial; COLOR: #000000">
<DIV>Thanks everyone for your replies.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In my original post I failed to EXACTLY reproduce the problem, in =
that capital letters were involved which I left out of the description.</DI=
V>
<DIV>For example, the id had been set up as "ID" serial primary key, and =
the sequencer was consequently named 'mytable_ID_seq' not 'mytable_id_seq' =
(he was stabbed to death by details!)</DIV>
<DIV>When I ran the select statement I DID reproduce the capital letters =
as they existed, but got the error I described.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In the effort to create a&nbsp;test sample I left out all caps and =
made everything lower case.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Viola! The problem disappeared!&nbsp; Sanity restored (for now).</DIV>=

<DIV>&nbsp;</DIV>
<DIV>That's it, no more caps for me!</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks again for everyone's efforts to help.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Fred</DIV>
<DIV><BR><BR>&gt;&gt;&gt; "Kevin Grittner" &lt;Kevin.Grittner@wicourts.gov&=
gt; 02/23/2012 11:34 AM &gt;&gt;&gt;<BR>"Fred Parkinson" &lt;FredP@abag.ca.=
gov&gt; wrote:<BR><BR>&gt; When I do \d I see the table and the sequencer =
under 'List of<BR>&gt; relations'.&nbsp; But when I run select * from =
mytable_id_seq;<BR>&gt; postgresql responds with: relation 'mytable_id_seq'=
 does not<BR>&gt; exist.<BR><BR>It works for me.&nbsp; Can you provide a =
small self-contained test case<BR>which demonstrates the problem?<BR><BR>Ho=
pefully you are aware of these functions, which might be easier:<BR><BR><A =
href=3D"http://www.postgresql.org/docs/8.4/interactive/functions-sequence.h=
tml">http://www.postgresql.org/docs/8.4/interactive/functions-sequence.html=
</A><BR><BR>-Kevin<BR></DIV></BODY></HTML>

--=__PartCDE3C90C.1__=--

--=__PartCDE3C90C.0__=--