From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Chuck Martin <clmartin(at)theombudsman(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Change from 9.6 to 11? |
Date: | 2018-12-20 21:02:28 |
Message-ID: | 19985.1545339748@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Chuck Martin <clmartin(at)theombudsman(dot)com> writes:
> I hope someone here can see something that eludes me. I've recently moved a
> database from PostgreSQL 9.6 to 11, and there are a few oddities. The
> following select statement returns zero rows when it should return one.
> This is one of a small number of records that exist, but are not returned
> by the query. When I include the main table, event, and any one of the
> associated tables, the record is returned, but no record is returned with
> the entire statement. All the primary keys (_pkey) and foreign keys (_fkey)
> are integers. The field I suspect as the possible culprit, event.InsBy, is
> a character column I'm converting to do a lookup on a primary key
> (integer): event.InsBy::int = usr.Usr_pkey. Maybe PG 11 doesn't recognize
> the same syntax for cast as PG 9.6? Or maybe I'm overlooking something else
> basic. Thanks for reading!
Maybe you've found a bug. Can you extract a self-contained case
exhibiting this behavior? Is this 11.0 or 11.1?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kumar, Virendra | 2018-12-20 21:02:35 | RE: Multiple LDAP Servers for ldap Authentication |
Previous Message | Ron | 2018-12-20 20:58:14 | Re: Watching for view changes |