pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
About pg_dump
4+ messages / 3 participants
[nested] [flat]

* About pg_dump
@ 2004-03-10 23:00  Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>
  0 siblings, 1 reply; 4+ messages in thread

From: Daniel Henrique Alves Lima @ 2004-03-10 23:00 UTC (permalink / raw)
  To: pgsql-sql

    Hi, everybody !

    I don't know if this is the best list to ask this question but if it 
doesn't, please forgive me (should i try pgsl-general, maybe ?)...
    We have a postgresql database in production and i've 2 questions 
about pg_dumpall boring me. We "dump" both ddl and data as SQL commands, 
so :

    1. Does the created sql script respect the database encoding (will 
chars be writen as utf-8 chars or iso-8859-1 char or ...) ?
    2. We've a bytea in one table. What exactly happens with the dumped 
data ? Is there any trouble with it ?

    I believe that we must to worry now (earlier). I don't want to 
expect until we must to restore database backup to descover that dumping 
data is corrupted :-)


                 Thanks in advance !!!!




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: About pg_dump
@ 2004-03-11 15:01  Rute Solipa <rutes@eselx.ipl.pt>
  parent: Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>
  0 siblings, 1 reply; 4+ messages in thread

From: Rute Solipa @ 2004-03-11 15:01 UTC (permalink / raw)
  To: email_daniel_h@yahoo.com.br; pgsql-sql

hi,

i had to restore a database from a pg_dump and i'm having problems with the
encoding.
it seems that the pg_dump command doesn't keep the encoding information.
does anybody can help me resolve this problem.

thanks

rute



----- Original Message -----
From: "Daniel Henrique Alves Lima" <email_daniel_h@yahoo.com.br>
To: <pgsql-sql@postgresql.org>
Sent: Wednesday, March 10, 2004 11:00 PM
Subject: [SQL] About pg_dump


>     Hi, everybody !
>
>     I don't know if this is the best list to ask this question but if it
> doesn't, please forgive me (should i try pgsl-general, maybe ?)...
>     We have a postgresql database in production and i've 2 questions
> about pg_dumpall boring me. We "dump" both ddl and data as SQL commands,
> so :
>
>     1. Does the created sql script respect the database encoding (will
> chars be writen as utf-8 chars or iso-8859-1 char or ...) ?
>     2. We've a bytea in one table. What exactly happens with the dumped
> data ? Is there any trouble with it ?
>
>     I believe that we must to worry now (earlier). I don't want to
> expect until we must to restore database backup to descover that dumping
> data is corrupted :-)
>
>
>                  Thanks in advance !!!!
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: About pg_dump
@ 2004-03-11 16:03  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Rute Solipa <rutes@eselx.ipl.pt>
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2004-03-11 16:03 UTC (permalink / raw)
  To: Rute Solipa <rutes@eselx.ipl.pt>; +Cc: email_daniel_h@yahoo.com.br; pgsql-sql

"Rute Solipa" <rutes@eselx.ipl.pt> writes:
> it seems that the pg_dump command doesn't keep the encoding information.

As of 7.4.2 it does emit a SET client_encoding.

In prior releases, if you are manually creating the destination database
then you need to be careful to create it with the same encoding as before.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: About pg_dump
@ 2004-03-11 21:13  Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Daniel Henrique Alves Lima @ 2004-03-11 21:13 UTC (permalink / raw)
  To: pgsql-sql

    I've made a test and it seems ok to me. I'm using utf-8 encoding 
under postgresql 7.3.3.

Tom Lane wrote:

>"Rute Solipa" <rutes@eselx.ipl.pt> writes:
>  
>
>>it seems that the pg_dump command doesn't keep the encoding information.
>>    
>>
>
>As of 7.4.2 it does emit a SET client_encoding.
>
>In prior releases, if you are manually creating the destination database
>then you need to be careful to create it with the same encoding as before.
>
>			regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>  
>





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2004-03-11 21:13 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-03-10 23:00 About pg_dump Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>
2004-03-11 15:01 ` Rute Solipa <rutes@eselx.ipl.pt>
2004-03-11 16:03   ` Tom Lane <tgl@sss.pgh.pa.us>
2004-03-11 21:13     ` Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox