[PATCHES] [pgsql-hackers-win32] pg_ctl --help

> pg_ctl --help > ---skiped--- > -P user name of account to register PostgreSQL server > -U password of account to register PostgreSQL server > ---skiped--- > > I think that isn't right ;) Good thinking... :-) Patch attached (but probably easier for any committer to make the c

Re: [PATCHES] build infrastructure for extensions v3

Dear Peter, > I am still opposed to adding more targets of the form "light-install", It is a renaming of the previous 'install' target, as the new install is the previous 'server-install', so it is no different from the current status. I let 'light-install' as a compromise wrt Tom view that th

Re: [PATCHES] build infrastructure for extensions v3

Patch withdrawn by author. --- Fabien COELHO wrote: > > Dear patchers, > > Please find attached version number 3 for a patch to enable extensions > such as contribs or external add-ons to be installed simply with an > alre

Re: [PATCHES] serverlog rotation/functions

Path withdrawn by author. --- Andreas Pflug wrote: > Updated version. > > Only timestamp of fresh logfile in shared mem, with sanity checks. > On SIGHUP, timestamp is checked if rotation was issued, as well as > changed lo

Re: [PATCHES] add missing options to pg_dumpall

Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches It will be applied as soon as one of the PostgreSQL committers reviews and approves it. --- \S

Re: [PATCHES] add missing options to pg_dumpall

Oops, patch coming from Christopher. Removed. --- Stefan Kaltenbrunner wrote: > Bruce Momjian wrote: > > Patch applied. Thanks. > > thanks - that's wonderful news :-) > > However the patch as it went in has a minor cosme

Re: [PATCHES] [pgsql-hackers-win32] pg_ctl --help

Patch applied. Thanks. --- Claudio Natoli wrote: > > > pg_ctl --help > > ---skiped--- > > -P user name of account to register PostgreSQL server > > -U password of account to register PostgreSQL server >

Re: [PATCHES] add missing options to pg_dumpall

Stefan Kaltenbrunner wrote: > Bruce Momjian wrote: > > Patch applied. Thanks. > > thanks - that's wonderful news :-) > > However the patch as it went in has a minor cosmetic issues with the > display of the --help output. > Maybe something like the attached patch should be applied to restore >

Re: [PATCHES] [HACKERS] possibly updating techdocs; mysql2pgsql on gborg

hi, just a contrib/mysql/README patch. Somehow the links got reversed. 5c5 < http://gborg.postgresql.org/project/mysql2psql/projdisplay.php --- > http://www.omnistarinc.com/~fonin/downloads.php#my2pg 9c9 < Another tool, mysql2pgsql, can be found at: --- > A third tool, mysql2pgsql.pe

Re: [PATCHES] [HACKERS] possibly updating techdocs; mysql2pgsql on gborg

Thanks, fixed. --- joe speigle wrote: > hi, > just a contrib/mysql/README patch. Somehow the links got reversed. > > 5c5 > < http://gborg.postgresql.org/project/mysql2psql/projdisplay.php > --- > > http://www.omni

[PATCHES] win32 readline

Readline is pretty badly broken under mingw. Basically, it disables the alt-gr key, which renders psql almost useless on most locales (no way to type backslash, and a whole lot of other characters, for example). This patch disables readline on win32. (meaning it's back to working the way it did in

[PATCHES] initdb authentication

Ok, here is one more try at the initdb default authentication stuff. This one adds the switches "--ident" and "--trust", which will configure pg_hba.conf with ident and trust authentication respectively. If trust authentication is selected, a warning is written to pg_hba.conf. The old switches for

Re: [PATCHES] initdb authentication

Magnus Hagander wrote: > This one makes it mandatory to pick some kind of authentication. If > that's not wanted, it's easy to change it to default to trust (which > I think is wrong, but we've been through that already..) I don't think I like any of this. Sooner rather than later, people need t

Re: [PATCHES] initdb authentication

Peter Eisentraut wrote: > Magnus Hagander wrote: > > This one makes it mandatory to pick some kind of authentication. If > > that's not wanted, it's easy to change it to default to trust (which > > I think is wrong, but we've been through that already..) > > I don't think I like any of this. Soon

Re: [PATCHES] initdb authentication

On Thu, Jul 15, 2004 at 11:20:46PM +0200, Peter Eisentraut wrote: > Magnus Hagander wrote: > > This one makes it mandatory to pick some kind of authentication. If > > that's not wanted, it's easy to change it to default to trust (which > > I think is wrong, but we've been through that already..) >

Re: [PATCHES] initdb authentication

Bruce Momjian <[EMAIL PROTECTED]> writes: > I think the basic problem is that right now there is no way to do an > initdb and have it be secure _before_ you edit pg_hba.conf. That isn't > acceptable. If I am on an insecure machine, the window if time between > initdb and editing of pg_hba.conf is

Re: [PATCHES] initdb authentication

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > I think the basic problem is that right now there is no way to do an > > initdb and have it be secure _before_ you edit pg_hba.conf. That isn't > > acceptable. If I am on an insecure machine, the window if time between > > initdb and

Re: [PATCHES] [subxacts] Savepoint syntax

On Wed, Jul 14, 2004 at 03:03:02PM -0400, Alvaro Herrera wrote: > Please test, review and apply. If anyone is able to crash the server > using this I'll be most interested. I just noticed that the "misc" regression test is generated, and so it needs to be patched ... interdiff output attached.