Re: Resolving 8.4 open items - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Resolving 8.4 open items
Date
Msg-id 4A2FF337.7060009@hagander.net
Whole thread Raw
In response to Resolving 8.4 open items  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Resolving 8.4 open items  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> If we are to make the proposed schedule for 8.4 (ie, wrap RC1 tomorrow)
> we've got to get pretty hard-nosed about closing out the open items at
> http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items
> 
> The current list is:
> 
> * do we need to worry about re-encoding file path names?
> 
> There is perhaps a real issue here, but it's not been explained nearly
> to my satisfaction: I do not understand how we should determine which
> encoding should be passed to the filesystem (but surely that shouldn't
> vary with the per-database locale), and it's also unclear why we
> shouldn't assume the value of PGDATA is already in that encoding.
> Perhaps the issue really applies only to file paths supplied to COPY,
> in which case the proposed patch is fixing it in the wrong place.
> I think we should just punt this question to TODO.

Is there really something new here for 8.4? Haven't we lived with this
same thing previously?

If it's not a regression, +1 for punting.


-- Magnus HaganderSelf: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PlannerInfo Structure
Next
From: Josh Berkus
Date:
Subject: Re: Multicolumn index corruption on 8.4 beta 2