On Wed, 2013-07-03 at 20:53 +0900, Ian Lawrence Barwick wrote:
> 2013/7/3 Jiří Hlinka :
> > Hi All,
> >
> > I have a 8.4 server and I'd like to use --section parameter of pg_dump and
> > pg_restore, which is available only in 9.2.
> >
> > 1. Is it, in general, safe to use 9.2 tools on 8.4 server?
2013/7/3 Jiří Hlinka :
> Hi All,
>
> I have a 8.4 server and I'd like to use --section parameter of pg_dump and
> pg_restore, which is available only in 9.2.
>
> 1. Is it, in general, safe to use 9.2 tools on 8.4 server? AFAIK the tools
> are backward compatible, at least in case of plain SQL comm
Hi All,
I have a 8.4 server and I'd like to use --section parameter of pg_dump and
pg_restore, which is available only in 9.2.
1. Is it, in general, safe to use 9.2 tools on 8.4 server? AFAIK the tools
are backward compatible, at least in case of plain SQL commands it should
be compatible, right
"Matt Janssen" writes:
> When migrating our Postgres databases from 32 to 64-bit systems, including
> large binary objects, how well will this work?
> 32-bit server) pg_dump --format=c --blobs --file=backup.pg mydb
> 64-bit server) pg_restore -d mydb backup.pg
Should be fine; but remember that o
When migrating our Postgres databases from 32 to 64-bit systems, including
large binary objects, how well will this work?
32-bit server) pg_dump --format=c --blobs --file=backup.pg mydb
64-bit server) pg_restore -d mydb backup.pg
I'm hoping that PG's compressed custom archive format is
On Tue, Apr 08, 2008 at 04:52:23PM -0300, Sergio Gabriel Rodriguez wrote:
> needs of others which can't be found because the script will generate
> them later. How can I make an orderer sql dump???
Use the custom format, use pg_restore to get the catalogue, and then edit
that catalogue to re-order
"Sergio Gabriel Rodriguez" <[EMAIL PROTECTED]> writes:
> I'm using postgresql 7.4, I have a problem with pg_dump/pg_restore. I
> want to back and restore only one schema from my db (I did it), but
> when I restore it, postgresql found errors in some views, this ones
> needs of others which can't be
On Tue, Apr 08, 2008 at 04:52:23PM -0300, Sergio Gabriel Rodriguez wrote:
> I'm using postgresql 7.4, I have a problem with pg_dump/pg_restore. I
> want to back and restore only one schema from my db (I did it), but
> when I restore it, postgresql found errors in some views, this ones
> needs of o
Hi for all, first sorry for my english is not good.
I'm using postgresql 7.4, I have a problem with pg_dump/pg_restore. I
want to back and restore only one schema from my db (I did it), but
when I restore it, postgresql found errors in some views, this ones
needs of others which can't be found bec
I had a similar experience when we upgraded from 7.4 to 8.1.4.
When we attempted the restore in 8.1.4 / UTF8, it failed and told us the offending row. We edited the original database to correct the data and retried. There were several ofending rows, but fortunatley for the exact same value, so we c
.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Benjamin Krajmalnik
> Sent: Thursday, October 05, 2006 12:03 PM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] pg_dump/pg_restore problem
>
> I have a database which has UTF8 e
I have a database which has UTF8 encoding enabled (why? I am really not
sure why I did tihs other than the source of the data is windows and I
had some issues with characters > ascii 128 being sent across from some
of the Windows event logs).
The problem which I am having is as follows:
The data
On Tue, Nov 29, 2005 at 02:35:12PM -0500, Colton Smith wrote:
> Hi:
>
> Let's say I have a database comprised of tables scattered over several
> tablespaces. Suppose I need to move the database to another server and
> I can't
> use the same pathnames for the tablespaces. Am I out of luck when
Hi:
Let's say I have a database comprised of tables scattered over several
tablespaces. Suppose I need to move the database to another server and
I can't
use the same pathnames for the tablespaces. Am I out of luck when it
comes to using pg_dump and pg_restore?
Thanks!
-
Title: Re: [ADMIN] pg_dump, pg_restore, insert vs copy
The dump file is binary
format when using:
pg_dump -Fc --compress=9
From: Uwe C. Schroeder
[mailto:[EMAIL PROTECTED]Sent: Thu 3/24/2005 8:57 PMTo: Lee
WuCc: Tom Lane; pgsql-admin@postgresql.orgSubject: Re:
[ADMIN] pg_dump
>
> Thanks,
>
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 24, 2005 9:11 AM
> To: Lee Wu
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_dump, pg_restore, insert vs copy
>
> "Lee Wu" <[EMAIL PR
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Is there any reason why we don't use a binary storage in custom format
> dumps? I mean, we could open a binary cursor and write the results to
> the file, and read it back at restore time. This is just handwaving of
> course.
> I guess the reason is c
On Thu, Mar 24, 2005 at 10:52:06AM -0500, Tom Lane wrote:
> "Lee Wu" <[EMAIL PROTECTED]> writes:
> > When I use pg_dump to back up the whole database and then pg_restore an
> > individual table,
> > pg_restore uses COPY. Great.
> > When I use pg_dump to back up an individual table and pg_restore i
I believe you're right.
Any easy way to find out if -d was used if dump is done someone else?
Thanks,
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 24, 2005 9:11 AM
To: Lee Wu
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_dump, pg_re
"Lee Wu" <[EMAIL PROTECTED]> writes:
> MY OS command is:
> pg_restore -v -t mytable -d mydb -U postgres -R my.dmp
That doesn't prove a thing; the question is what you typed at pg_dump.
Thinking about it, I wonder if you did "pg_dump -d mydb ..."
-d means something different to pg_dump than pg_res
rg
Subject: Re: [ADMIN] pg_dump, pg_restore, insert vs copy
"Lee Wu" <[EMAIL PROTECTED]> writes:
> When I use pg_dump to back up the whole database and then pg_restore
an
> individual table,
> pg_restore uses COPY. Great.
> When I use pg_dump to back up an individual tabl
"Lee Wu" <[EMAIL PROTECTED]> writes:
> When I use pg_dump to back up the whole database and then pg_restore an
> individual table,
> pg_restore uses COPY. Great.
> When I use pg_dump to back up an individual table and pg_restore it,
> pg_restore uses INSERT.
Not for me...
That decision is fixed
Hi,
When I use pg_dump to back up the whole database and then
pg_restore an individual table,
pg_restore uses COPY. Great.
When I use pg_dump to back up an individual table and
pg_restore it, pg_restore uses INSERT.
Method 1:
pg_dump mydb -R -Fc --compress=9 > method1.dmp
On Oct 1, 2004, at 10:12, Tore Halset wrote:
I am running 8.0.0-beta3 on Mac OS X 10.3.5 and 8.0.0-beta2-dev3
(pginstaller) on windows 2000. I have two databases. The dumpfile
(format c) for database 1 is 150MB and the dumpfile for database 2 is
2GB.
Dumping the databases on the mac worked. I h
Hello.
I am running 8.0.0-beta3 on Mac OS X 10.3.5 and 8.0.0-beta2-dev3
(pginstaller) on windows 2000. I have two databases. The dumpfile
(format c) for database 1 is 150MB and the dumpfile for database 2 is
2GB.
Dumping the databases on the mac worked. I have loaded the dumpfiles in
another d
ECTED]'
Subject: Re: [ADMIN] PG_DUMP / PG_RESTORE
Laurens Wagemakers <[EMAIL PROTECTED]> writes:
> Running postgresql 7.1.3 on Solaris 9:
> Restoring a database from a RH 7.3 Postgresql 7.1 version
You generally aren't going to be able to restore a dump into an older
versio
Laurens Wagemakers <[EMAIL PROTECTED]> writes:
> Running postgresql 7.1.3 on Solaris 9:
> Restoring a database from a RH 7.3 Postgresql 7.1 version
You generally aren't going to be able to restore a dump into an older
version without some manual labor.
> CREATE SEQUENCE "live_autoincrement" start
Hi all,
Running postgresql 7.1.3 on Solaris 9:
Restoring a database from a RH 7.3 Postgresql 7.1 version
Get the message:
CREATE SEQUENCE "live_autoincrement" start 1 increment 1 maxvalue
92233720368547
75807 minvalue 1 cache 1;
ERROR: parser: parse error at or near "9223372036854775807"
(set q
On 1/12/04 11:17 AM, Sai Hertz And Control Systems wrote:
> Dear Alexey Bobkov ,
>> Then a try to restore my data:
>> pg_restore /path_to_database/backup/db_backup.file
>> and get next error
>> pg_restore: [archiver] input file does not appear to be a valid archive
>
> Use psql instead with comman
Dear Alexey Bobkov ,
Then a try to restore my data:
pg_restore /path_to_database/backup/db_backup.file
and get next error
pg_restore: [archiver] input file does not appear to be a valid archive
Use psql instead with command
psql -U username databasename -f yourdb_file.sql
Yes you will have to edi
Tom Lane wrote:
Alexey Bobkov <[EMAIL PROTECTED]> writes:
I have been dumping my database with next options:
pg_dump -f /path_to_database/backup/db_backup.file -Z 9 database_name
and get db_backup.file file.
This is giving you a plain SQL-script dump file. To restore, feed it
into psql.
No :)
Alexey Bobkov <[EMAIL PROTECTED]> writes:
> I have been dumping my database with next options:
> pg_dump -f /path_to_database/backup/db_backup.file -Z 9 database_name
> and get db_backup.file file.
This is giving you a plain SQL-script dump file. To restore, feed it
into psql.
PostgreSQL 7.3.2
I have been dumping my database with next options:
pg_dump -f /path_to_database/backup/db_backup.file -Z 9 database_name
and get db_backup.file file.
Then a try to restore my data:
pg_restore /path_to_database/backup/db_backup.file
and get next error
pg_restore: [archiver] input f
33 matches
Mail list logo
