Contents
What does PG dumpall do in PostgreSQL script?
The script file contains SQL commands that can be used as input to psql to restore the databases. It does this by calling pg_dump for each database in the cluster. pg_dumpall also dumps global objects that are common to all databases, that is, database roles and tablespaces. ( pg_dump does not save these objects.)
Can a dmp file be created using PG _ dump?
I have a dmp file I have created using pg_dump encoded in WIN1252. What I would like to do is import it using pg_restore to a database on a Linux machine. The problem is that on the windows machine postgreSQL recognizes the encoding WIN1252 but not the CP1252 encoding (they both are identical just different names for the same standard).
Why do I have to wait for PG _ dumpall to return?
By default, pg_dumpall will wait for all files to be written safely to disk. This option causes pg_dumpall to return without waiting, which is faster, but means that a subsequent operating system crash can leave the dump corrupt. Generally, this option is useful for testing but should not be used when dumping data from production installation.
Why is PostgreSQL unable to set client encoding to win1252?
EDIT: Actually, upon further investigation, postgreSQL does not understand cp1252. The iconv linux command used to convert a text file from one encoding to another understands cp1252 and not win1252 and thats where I got it from. On the Linux machine, I still cannot set the client encoding to WIN1252. This is the error message:
Do you need superuser privileges for PG dumpall?
Since pg_dumpall reads tables from all databases you will most likely have to connect as a database superuser in order to produce a complete dump. Also you will need superuser privileges to execute the saved script in order to be allowed to add users and groups, and to create databases.
How to get PG _ dump to include create user?
How to get pg_dump to include all the commands:create user command,grant connect on database test to rdstest etc. pg_dump can not do that, because pg_dump only dumps a single database and that information is not part of one database, but stored globally in the Postgres “cluster”.
Why does PG dumpall only quote reserved identifiers?
By default, pg_dumpall quotes only identifiers that are reserved words in its own major version. This sometimes results in compatibility issues when dealing with servers of other versions that may have slightly different sets of reserved words. Using –quote-all-identifiers prevents such issues, at the price of a harder-to-read dump script.