From: | George Woodring <george(dot)woodring(at)iglass(dot)net> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pavel(dot)stehule(at)gmail(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Plpgsql search_path issue going from 9.3 to 9.6 |
Date: | 2018-11-13 15:37:28 |
Message-ID: | CACi+J=RYQfS01odLT6aag9jqd8jA2Xe_KYcYCCnfb=CfoMThpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
CREATE OR REPLACE VIEW tickets AS
SELECT *, tableoid
FROM public.tickets
WHERE ( ticketsid IN (SELECT ticketsid
FROM machtick));
iGLASS Networks
www.iglass.net
On Tue, Nov 13, 2018 at 10:32 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 11/13/18 6:54 AM, George Woodring wrote:
> > The tickets view restricts which tickets can be seen by the schema.
> >
> > 9.3 must have created the view in the same column order as the table
> > (which is the case looking at one of our 9.3 databases which we have not
> > updated yet), which is why we never saw the issue before.
>
> What is the view definition?
>
> >
> > George
> > iGLASS Networks
> > www.iglass.net <http://www.iglass.net>
> >
>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | George Woodring | 2018-11-13 15:39:40 | Re: Plpgsql search_path issue going from 9.3 to 9.6 |
Previous Message | Adrian Klaver | 2018-11-13 15:32:53 | Re: Plpgsql search_path issue going from 9.3 to 9.6 |