Thread: A minor bug and a complaint

Hi all.

First off, PostgreSQL 7.2; pg_ctl script has a bug I'm unable to locate. When I try to run it, I get the following:

/usr/local/pgsql/bin/postmaster: invalid argument --

Somehow, "--" gets appended to the command line. No big deal, I can start postmaster manually.

My complaint is about one other "feature" - pg_dump. It doesn't dump database encoding. I have several databases on the
systemand they use different encodings ("UNICODE" and "LATIN2"). "pg_dump" forgets to add the encoding atribute for the
database,which is problematic.
 

Earlier versions didn't even have a man page stating how to create a database from SQL with encoding. In 7.2 at least
thatis in the docs"
 

CREATE DATABASE "www" WITH ENCODING = "UNICODE";

Any chance of pg_dump being corrected to dump encoding, as well?

Nix.

"Nikola Milutinovic" <Nikola.Milutinovic@ev.co.yu> writes:
> First off, PostgreSQL 7.2; pg_ctl script has a bug I'm unable to locate. When I try to run it, I get the following:

> /usr/local/pgsql/bin/postmaster: invalid argument --

> Somehow, "--" gets appended to the command line. No big deal, I can start postmaster manually.

A lot of other people use pg_ctl without any problem.  If you want us to
take this report seriously, you'll need to provide some details that'd
show why it's not working for you.  For instance, exactly how are you
invoking pg_ctl, in what environment, and on what platform?

> My complaint is about one other "feature" - pg_dump. It doesn't dump
> database encoding.

If you're speaking of pg_dump -C, that's fixed in current sources
(7.2.1-to-be).

            regards, tom lane