Kemin Zhou wrote:
If I have to organize an automatic nightly pg_dumpall, how do I handle
authentication ? I do not want to create a passwordless superuser (or
trust method in pg_hba.conf), and there is noone to enter the password
manually. Is there another recipe?
Thanks in advance for any
On Thu, Mar 25, 2004 at 06:04:10PM -0500, Chris Browne wrote:
The FSF web site then compares various variations on BSD licenses,
considering that there are some that they deem to be free (in their
terms), and that there are others that they deem to _NOT_ be free
(again in their terms).
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Quale wrote:
| Chris Browne [EMAIL PROTECTED] writes:
|
|
|The FSF characterizes the PostgreSQL license as being an X11 style
|license. They felt a need to distinguish between different
|variations of licenses that are called 'BSD licenses.'
|
On Fri, 26 Mar 2004, Radu-Adrian Popescu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Quale wrote:
| Chris Browne [EMAIL PROTECTED] writes:
|
|
|The FSF characterizes the PostgreSQL license as being an X11 style
|license. They felt a need to distinguish between different
Dear List,
Is there a way to completely turn off case sensitivity of the names of
table, field, sequence, etc.?
In our case we used mixed-case names, and the names are unique. They
wouldn't collide even if they get turned into lowercase names.
Because of interfacing problems with other
Hi,
We have postgresql 7.4.1 running on Mac OS.we are
doing a conversion from mysql to postgres. I'm
importing the table dumps using copy command in
postgres. Copy takes 2 min to import 427938 rows in
one table and at the same time it takes more than 2
hrs for 2415768 rows.. no of columns are
On Thu, Mar 25, 2004 at 04:21:16 +,
Victor Sudakov [EMAIL PROTECTED] wrote:
Colleagues,
If I have to organize an automatic nightly pg_dumpall, how do I handle
authentication ? I do not want to create a passwordless superuser (or
trust method in pg_hba.conf), and there is noone to enter
I think you can get both benefits of multi-statement transactions for INSERT dumps
by doing subset copies ... without any changes in postgresql! The method I use is
developed for handling single table loads, but is still relatively painless even for
database dumps; however, it is limited to
On Mon, Mar 22, 2004 at 09:13:06 -0800,
Mark M. Huber [EMAIL PROTECTED] wrote:
That sounds like a brilliant idea, who do we say it to make it so?
It might be better to make this part of pg_restore, rather than pg_dump.
Mark H
-Original Message-
From: Naomi Walker [mailto:[EMAIL
Radu-Adrian Popescu [EMAIL PROTECTED] writes:
Doug Quale wrote:
| The Postgres license is a free software license that is GPL
| compatible.
Where GPL compatible means (possibly among other things) that I can get
a BSD-licensed Postgresql and turn it into a GPL-licensed MyPostgresql ?
Hi,
| The Postgres license is a free software license that is GPL
| compatible.
Where GPL compatible means (possibly among other things) that I can get
a BSD-licensed Postgresql and turn it into a GPL-licensed MyPostgresql ?
No, it means you can distribute the two together like on
On Fri, 26 Mar 2004, Hemapriya wrote:
Hi,
We have postgresql 7.4.1 running on Mac OS.we are
doing a conversion from mysql to postgres. I'm
importing the table dumps using copy command in
postgres. Copy takes 2 min to import 427938 rows in
one table and at the same time it takes more than 2
Title: RE: [Retrieved]RE: [ADMIN] backup and recovery
Oops, sorry for the typo in the psql command invocation. The output of the awk command in Step 3 is piped to
/usr/local/pgsql-7.4/bin/psql -d db_quux -f - -Atnq
(in the logging alternative it goes to
/usr/local/pgsql-7.4/bin/psql -d
13 matches
Mail list logo
