Re: Getting non_NULL right-side values on a non-matching join? - Mailing list pgsql-general

From Ken Tanzer
Subject Re: Getting non_NULL right-side values on a non-matching join?
Date
Msg-id CAD3a31UKkHsN4Hn_T0iFcZ8Bo5XrvU72ruuM7GpyOWBtKLJDWw@mail.gmail.com
Whole thread Raw
In response to Re: Getting non_NULL right-side values on a non-matching join?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Getting non_NULL right-side values on a non-matching join?
List pgsql-general
Thanks Tom.  The workaround seems harmless, even good coding practice, so it's all good on my end.  If it were useful to you I'd gladly build and test it, but I doubt that's the case.  But just say the word!  Otherwise it's just a question of time and priorities, and it seems likely to chew up at least a few hours if I'm careful about it.

OTOH, if there were a very clear and credible page with good instructions on installing build environment + postgres (for say RHEL, Ubuntu & Fedora) that would install side by side with an existing installation (and how to remove it all cleanly) it would make me and maybe others more able/likely to test patches.  There may be such a page--I just didn't find it.  And I was somewhat dissuaded from building an RPM on my CentOs machine by the note in the Postgres wiki that the ubuntu packages allow "multiple versions more easily than other packaging schemes."

Just a thought.  I know all the information is out there and can be pieced together.  Like many computing endeavors, I'm sure the second time would be quick and easy, but likely not so much the first!

Cheers,
Ken


On Fri, Nov 22, 2013 at 8:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ken Tanzer <ken.tanzer@gmail.com> writes:
> On Fri, Nov 22, 2013 at 8:04 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I found a less nasty workaround: if you replace "my_field" by
>> "foo.my_field" in the SELECT list of boo_top_view, the problem goes away.

> I'm happy to be of assistance, but mostly glad it wasn't a me-bug! :)  I
> put an alias on every field reference in the view, and the problem did
> indeed go away.  Thank you very much for providing an easy workaround!

Great, I'm glad that was good enough for you.  There's a real fix
committed here:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=c0aa210f6ebab06ca3933c735c7c6d2b8bdd024e
but since you expressed some discomfort about patching source before,
it's probably best if you just work around it till we put out new
releases.

                        regards, tom lane



--
AGENCY Software  
A data system that puts you in control
100% Free Software
(253) 245-3801

learn more about AGENCY or
follow the discussion.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Getting non_NULL right-side values on a non-matching join?
Next
From: Tianyin Xu
Date:
Subject: "shared_buffers" and "temp_buffers" why manual and code are different?