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

From Magnus Hagander
Subject Re: 8.4 open items list
Date
Msg-id 49D4CC16.9030904@hagander.net
Whole thread Raw
In response to Re: 8.4 open items list  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 8.4 open items list  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Dave Page <dpage@pgadmin.org> writes:
>> On Thu, Apr 2, 2009 at 8:47 AM, Heikki Linnakangas
>> <heikki.linnakangas@enterprisedb.com> wrote:
>>> Now is the time to decide, before the PostgreSQL beta is out. I understand
>>> the pain inflicted on tools, but I don't think that's a good reason to not
>>> change it. People using a beta version of pgAdmin will should understand
>>> that it's not final yet and there can be small glitches like that.
> 
>> It's not about the changes the users see, it's about invalidating the
>> testing that's been done on the tools & interfaces and requiring last
>> minute changes to be made followed by re-testing.
> 
> Personally I think the naming decision is close enough to be a coin
> toss, and so either choice is fine with me.  However, I think it is
> Clearly Unacceptable for createdb's switches to be spelled differently
> than the underlying SQL command's options.  So it's not really "let's
> not change this" but "which one do you consider it more important to not
> change"?

pgAdmin uses the SQL commands, not the external commands. IIRC the only
external commands that are used are pg_dump[all], pg_restore, pg_ctl and
initdb. Is initdb on the list of tools that might be changed?

//Magnus



pgsql-hackers by date:

Previous
From: Steven Lembark
Date:
Subject: Re: [pgsql-www] Mentors needed urgently for SoC & PostgreSQL Student Internships
Next
From: Tom Lane
Date:
Subject: Re: "failed to commit client_encoding" explained