Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)
Date: 2011-03-05 17:55:41
Message-ID: 201103051855.41396.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Saturday 05 March 2011 18:43:31 Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I have a WIP patch fixing one of the two issues.
> >
> > Several places in selfuncs.c didn't setup collations. That lead for
> > example to errors during patternsel.
>
> Hmm. I have to say that this seems like quite the wrong way to go.
> If everyplace in the system that could be calling a collation-sensitive
> function has to be modified like this, we'll be fighting bugs of
> omission till h*ll freezes over. Why aren't we just setting
> finfo.fn_collation to DEFAULT_COLLATION_OID by default, or maybe better
> letting places that inspect it take zero as meaning default collation?
> Call sites should only need to call fmgr_info_collation() if they have
> an explicit non-default collation to pass in.
I wondered the same. On the other hand it makes errors like the one during
index build way much harder to catch...

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-05 17:59:50 Re: Sync Rep v19
Previous Message Tom Lane 2011-03-05 17:43:31 Re: Alpha4 release blockers (was Re: wrapping up this CommitFest)