MIME-Version: 1.0
References: <16991-bcaeaafa17e0a723@postgresql.org>
 <3896142.1620136761@sss.pgh.pa.us>
 <CAN19dyfQnRwz=+Ffnr4qfVddZDd7m7LKfuX1PmsFhYY5Z7SpQw@mail.gmail.com>
 <3904665.1620138892@sss.pgh.pa.us> <3976561.1620170328@sss.pgh.pa.us>
 <41d84eb3471bd6f42384f054c04573ad5c8d7aac.camel@cybertec.at>
 <4026666.1620228511@sss.pgh.pa.us>
In-Reply-To: <4026666.1620228511@sss.pgh.pa.us>
From: Federico <cfederico87@gmail.com>
Date: Wed, 5 May 2021 21:17:49 +0200
Message-ID: 
 <CAN19dyci7=80q3kLmh=h+B=zYYphcniCvB=AMVLQ3SeREwusYg@mail.gmail.com>
Subject: Re: BUG #16991: regclass is not case sensitive causing "relation does
 not exist" error
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a50ed505c19a0e5b"
Archived-At: 
 <https://www.postgresql.org/message-id/CAN19dyci7%3D80q3kLmh%3Dh%2BB%3DzYYphcniCvB%3DAMVLQ3SeREwusYg%40mail.gmail.com>
Precedence: bulk

--000000000000a50ed505c19a0e5b
Content-Type: text/plain; charset="UTF-8"

Thanks for the quick resolution.

Best,
Federico

Ps: sorry for the previous messages in html, I had not realized that the
client I was using were sending the replies like that.

On Wed, 5 May 2021 at 17:28, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Laurenz Albe <laurenz.albe@cybertec.at> writes:
> > On Tue, 2021-05-04 at 19:18 -0400, Tom Lane wrote:
> >> So what I was remembering was some text in the section about sequence
> >> functions.  That probably seemed appropriate when they were the only
> >> real use of regclass; but these days we have regclass-accepting
> functions
> >> all over, not to mention other OID alias types.  I propose the attached
> >> patch to move this info into the "Object Identifier Types" section.
>
> > That patch looks good to me.
> > I think it is an improvement to have that discussed under "data types".
>
> Pushed, thanks for reviewing.
>
>                         regards, tom lane
>

--000000000000a50ed505c19a0e5b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks for the quick resolution.</div><div><br></div>=
<div>Best,</div><div>Federico</div><div><br></div><div>Ps: sorry for the pr=
evious messages in html, I had not realized that the client I was using wer=
e sending the replies like that.<br></div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, 5 May 2021 at 17:28, Tom =
Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Laurenz Albe=
 &lt;<a href=3D"mailto:laurenz.albe@cybertec.at" target=3D"_blank">laurenz.=
albe@cybertec.at</a>&gt; writes:<br>
&gt; On Tue, 2021-05-04 at 19:18 -0400, Tom Lane wrote:<br>
&gt;&gt; So what I was remembering was some text in the section about seque=
nce<br>
&gt;&gt; functions.=C2=A0 That probably seemed appropriate when they were t=
he only<br>
&gt;&gt; real use of regclass; but these days we have regclass-accepting fu=
nctions<br>
&gt;&gt; all over, not to mention other OID alias types.=C2=A0 I propose th=
e attached<br>
&gt;&gt; patch to move this info into the &quot;Object Identifier Types&quo=
t; section.<br>
<br>
&gt; That patch looks good to me.<br>
&gt; I think it is an improvement to have that discussed under &quot;data t=
ypes&quot;.<br>
<br>
Pushed, thanks for reviewing.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 regards, tom lane<br>
</blockquote></div>

--000000000000a50ed505c19a0e5b--