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 Hagander Self: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
