`pg_restore`, when run without a database name, outputs a text dump to stdout; you can send that elsewhere with `-f` or with I/O redirection.

    pg_restore -f mydatabase.sql mydatabase.dump 

Note that you must ensure there&#39;s no `PGDATABASE` environment variable set, or it&#39;ll try to connect to that database.

The fastest method that I&#39;ve used was:

    pg_restore -f mybinaryfile.backup &gt; mysqlfile.sql

No special flags, since pg_restore just spits it out to stdout.

Note that if you run multiple clusters, the restore command may not like the default version...

&gt; pg_restore: [archiver] unsupported version (1.12) in file header

In that case you have to specify the version, host and port as in:

    pg_restore --cluster 9.1/localhost:5433 -f db.sql db.pgsql

(note that the `host:port` info is ignored with the -f option.)

The port (5433) can be determined using the `pgsql` command as in:

    pgsql --port 5433 template1

When `pgsql` connects, it writes a comment such as:

&gt; psql (9.3.6, server 9.1.13)

This means you are running pgsql 9.3.6 and that port 5433 references server 9.1.13.

If you are not sure which ports are currently used, you may use the `netstat` command as in:

    sudo netstat -a64np | grep LISTEN | grep postgres

The `sudo` is required for the `-p` option which prints the process name. That gives you a list of ports (usually TCP and UDP ports).

Finally, on a Debian/Ubuntu system, you can get a list of installed clusters with the `dpkg -l` command as in:

    dpkg -l &#39;*postgres*&#39;

The list of entries that start with &#39;ii&#39; (left most column) are currently installed. You, of course, have similar commands for other Unices to help you determine installed versions.

When I use the following code with Data matrix `X` of size (952,144) and output vector `y` of size (952), `mean_squared_error` metric returns negative values, which is unexpected. Do you have any idea?


    from sklearn.svm import SVR
    from sklearn import cross_validation as CV

    reg = SVR(C=1., epsilon=0.1, kernel=&#39;rbf&#39;)
    scores = CV.cross_val_score(reg, X, y, cv=10, scoring=&#39;mean_squared_error&#39;)

all values in `scores` are then negative.

scikit-learn cross validation, negative values with mean squared error

We can localize an image in the `File Inspector` using `Localize...` like this:

![enter image description here][1]

Then we can get this:

![enter image description here][2]

But now, I use Images.xcassets to manage my images in my iOS project, how should I localize these images in Images.xcassets?


  [1]: http://i.stack.imgur.com/4cPpA.png
  [2]: http://i.stack.imgur.com/GIoJg.png

How to localize the images in Images.xcassets?

I do want to search for some data inside a database dump but these dumps are using the binary-compressed format (`PGDMP` header). 

How can I convert these to SQL without restoring them?

How do I convert a binary pgdump (compressed) to a plain SQL file?

<p>I do want to search for some data inside a database dump but these dumps are using the binary-compressed format (<code>PGDMP</code> header).</p>
<p>How can I convert these to SQL without restoring them?</p>


So I have an array of user ids. Is there a way in rails console to query all of these user&#39;s with the array

something like

    ids = [1, 2, 3, 4]
    
    users = User.find(ids)

and have it return all 4 users?

Rails Console find users by array of ids

I just installed posgresql with homebrew and when I go on to type the command

    psql
I get the following error:

    dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.6.2.dylib
    Referenced from: /usr/local/bin/psql
    Reason: image not found
    [1]    69711 trace trap  psql

Does anyone have any idea about what&#39;s wrong?

Library not loaded: /usr/local/opt/readline/lib/libreadline.6.2.dylib

What is the best way to find records with duplicate values across multiple columns using Postgres, and Activerecord?

I found this solution [here][1]:

`User.find(:all, :group =&gt; [:first, :email], :having =&gt; &quot;count(*) &gt; 1&quot; )`

But it doesn&#39;t seem to work with postgres. I&#39;m getting this error:

PG::GroupingError: ERROR:  column &quot;parts.id&quot; must appear in the GROUP BY clause or be used in an aggregate function


  [1]: https://stackoverflow.com/a/4564716/2229277

Find rows with multiple duplicate fields with Active Record, Rails &amp; Postgres

How can I **list all the tables** of a PostgreSQL database and **order them by size**?

postgresql list and order tables by size

I have imported 100 of tables in Postgres from MSSql server 2008 through tool which created all the tables along with their columns in **capital letter**. Now if I want to make a data view from table e.g - STD_TYPE_CODES as-

    select * from STD_TYPE_CODES
I am getting following error-

    ERROR:  relation &quot;std_type_codes&quot; does not exist
    LINE 1: select * from STD_TYPE_CODES
                      ^
    ********** Error **********
    ERROR: relation &quot;std_type_codes&quot; does not exist
    SQL state: 42P01
    Character: 15
I know I can put the quotes around the table name as-

    select * from &quot;STD_TYPE_CODES&quot;
But as I have worked with MSSql Server, there is no such kind of issue.
So is there any way to get rid of this? Please help.


Postgres Case Sensitivity

I&#39;m trying to pg_dump a SQL database on a remote server in our DMZ. There are 2 problems. 

1) there is not a lot of space left on the remote server so the normal command run to locally backup the database 
`pg_dump -C database &gt; sqldatabase.sql.bak`  won&#39;t work due to space issues. 


2) I also can&#39;t run the other version of pg_dump command to dump database from remote server to local server using: 

    pg_dump -C -h remotehost -U remoteuser db_name | psql localhost -U localuser db_name

as the server is in our DMZ and port 5432 is blocked. What I&#39;m looking to see is if it is possible to pg_dump the database and immediatly save it (ssh or some other form) as a file to a remote server. 
What I was trying was:   `pg_dump -C testdb | ssh admin@ourserver.com | &gt; /home/admin/testdb.sql.bak` 

Does anyone know if what i am trying to achieve is possible? 

pg_dump postgres database from remote server when port 5432 is blocked

I have a live server and development box, call them live and dev respectively both running postgresql. I can see both and manage both with pgadmin4 without trouble, and both are fully functional the one behing a live website and the other when I run by website in debug mode on the my dev box. Pretty ordinary setup.

For years I have been running the same bash script I wrote that dumps the live database then restores it on the dev box so I have the latest live snapshot to work with.

Today this fails me with the titled message:
```
pg_restore: [archiver] unsupported version (1.14) in file header
```

I have tried to diagnose this, and searched extensively on-line but am bedeviled and have failed so here I am cap in hand for expertise.

To help I will share the following:

```
$ pg_dump --version
pg_dump (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
$ pg_restore --version
pg_restore (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
$ pg_dump --host=live.lan --port=5432 --dbname=mydb --username=myuser --format=custom &gt; test.backup
$ ls -l test.backup 
-rw-r--r-- 1 bernd bernd 2398358 Dec 23 23:40 test.backup
$ file test.backup 
test.backup: PostgreSQL custom database dump - v1.14-0
$ pg_restore --dbname=mydb test.backup 
pg_restore: [archiver] unsupported version (1.14) in file header
```

Given pg_dump and pg_restore are identical versions and:

```
$ which pg_dump
/usr/bin/pg_dump
$ which pg_restore
/usr/bin/pg_restore
$ ls -l /usr/bin/pg_dump /usr/bin/pg_restore
lrwxrwxrwx 1 root root 37 Nov 14 23:23 /usr/bin/pg_dump -&gt; ../share/postgresql-common/pg_wrapper
lrwxrwxrwx 1 root root 37 Nov 14 23:23 /usr/bin/pg_restore -&gt; ../share/postgresql-common/pg_wrapper
```

I can see they are not just identical versions but are run by the same wrapper script (which happens to be a perl script - now that&#39;s a language you don&#39;t see much anymore and I used to code in extensively)

So I&#39;m left totally perplexed. Thinking there may be a version issue with the live machine:

```
$ ssh live.lan
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-72-generic x86_64)
$ which pg_dump
/usr/bin/pg_dump
$ which pg_restore
/usr/bin/pg_restore
$ pg_dump --version
pg_dump (PostgreSQL) 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)
$ pg_restore --version
pg_restore (PostgreSQL) 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)
```

I can see the live box does have slightly older version of pg_dump (which would only matter if pg_dump on my dev box somehow used a RPC to the live box to run its pg_dump).

Now there is maybe a small clue in the fact that my dev box has seen a few postgresql upgrades come through and so for example:

```
$ pg_lsclusters
Ver Cluster Port Status Owner    Data directory              Log file
10  main    5432 online postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
11  main    5433 online postgres /var/lib/postgresql/11/main /var/log/postgresql/postgresql-11-main.log
12  main    5434 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
```

The 11 and 12 clusters remain unused as evidenced by empty log files. I&#39;m using 10. But I do notice that:

```
$ psql --version
psql (PostgreSQL) 12.1 (Ubuntu 12.1-1.pgdg18.04+1)
$ ssh live.lan
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-72-generic x86_64)
$ psql --version
psql (PostgreSQL) 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)
```

which is mildly fishy but again not obviously a cause or related:

 1. I am using pg_dump not psql
 2. I am using only the dev boxes pg tools not the live boxes (they should be irrelevant, the whole data transfer theoretically over port 5432 on the live box which delivers a databse dump to pg_dump on my dev box.

Here are the clusters on the love box and it&#39;s over port 5432 that on live.lan I&#39;m running pg_dump!

```
$ pg_lsclusters 
Ver Cluster Port Status Owner    Data directory           Log file
10  main    5432 online postgres /data/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
```

I am deeply perplexed and hamstrung at present by this. Would deeply appreciate forward moving clues. If I am compelled to fish around in the dark I will probbaly uninstall postgres 11 and 12 again and see if that helps, else I will end up having to trace `/usr/share/postgresql-common/pg_wrapper` to see how and where the two paths of pg_dump and pg_restore diverge down incompatible version paths. 

**Update:**

A further clue I have uncovered, that permits me a workaround but simply deepens the mystery is as follows:

```
$ sudo -u postgres pg_dump --host=live.lan --port=5432 --dbname=mydb --username=myuser --format=custom &gt; test.backup
$ sudo -u postgres /usr/lib/postgresql/10/bin/pg_dump --host=live.lan --port=5432 --dbname=mydb --username=myuser --format=custom &gt; test2.backup
$ sudo -u postgres pg_restore -l test.backup
pg_restore: [archiver] unsupported version (1.14) in file header
$ sudo -u postgres pg_restore -l test2.backup
... produces listing of contents ...
$ sudo -u postgres pg_dump --version
pg_dump (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
$ sudo -u postgres /usr/lib/postgresql/10/bin/pg_dump --version
pg_dump (PostgreSQL) 10.11 (Ubuntu 10.11-1.pgdg18.04+1)
```

That is perplexing beyond belief. The only possible explanations:

 1. in spite of reporting identical version numbers the two pg_dumps are different. I would rule this out as beyond belief.
 2. pg_dump runs pg_wrapper which runs /usr/lib/postgresql/10/bin/pg_dump with some mystery argument(s) that break it! 

The second is plausible, and will require me to instrument pg_wrapper to diagnose. 

**Update 2:**

And one instrumentation of pg_wrapper later. It eventuates that pg_dump runs pg_wrapper which runs `/usr/lib/postgresql/12/bin/pg_dump` yet it runs `/usr/lib/postgresql/10/bin/pg_restore` ... Go figure! Starting to think this a postgresql version interoperability bug!

**Update 3:**

Looking deeper into `pg_wrapper`, nailed the cause, and yes I&#39;d argue it&#39;s a pg_wrapper bug of a kind though it may be debatable, hardly though IMHO. Here&#39;s what it does:

If `--host` is provided then it uses the newest version of postgresql installed (12 in my case and this is for pg_dump, so pg_dump 12 creates the dump)

If `--host` is not provided then it consults the user config (10 in my case, and this is for pg_restore, so pg_restore 10 is run and it can&#39;t read a file created by pg_dump 12).

So why is this a bug? Because I have a use config, and I&#39;d like it respected whether or not I&#39;m talking to a remote host. More to the point if I specify a host I certainly don&#39;t expect to use the latest local version ignoring local config. I&#39;d expect either to respect local config (as is the case when no remote host is specified) or try to match the rmeote hosts version. Arbitrarily leaning on the latest installed version is IMHO deeply questionable.

BUT it turns out there is a workaround that works. Essentially instead of:

```
sudo -u postgres pg_restore -l test.backup
```

this works:

```
sudo -u postgres pg_restore --host=localhost -l test.backup
```

By specifying the host ironically we force it to ignore local configs and use the newest version of pg_restore which seems to work fine restoring to a PG 10 cluster. 

pg_restore: [archiver] unsupported version (1.14) in file header

I take backup using 

    pg_dump db_production &gt; postgres_db.dump

and then I copy it to localhost using scp.

Now when I import on my local db it gives an error 

    pg_restore: [archiver] input file appears to be a text format dump. Please use psql.

by using commad line

    pg_restore -d db_development postgres_db.dump


input file appears to be a text format dump. Please use psql

I just upgraded to postgres 10.2 on mac os which matches 10.2 on heroku.  I&#39;m trying to download a copy of the database and restore it locally.  Before the upgrade the restore would work fine.

I run

    pg_restore --verbose --clean --no-acl --no-owner -h localhost -d database_name backup.dump

but I am getting this error:

&gt;pg_restore: [archiver] unsupported version (1.13) in file header

The database appears to be working OK.  It&#39;s a rails app and I upgraded the pg gems.  I can run `rake db:create` and `db:migrate` just fine.  


Content Type	Original Author	Original Content on Stackoverflow
Question	sorin	View Question on Stackoverflow
Solution 1 - Postgresql	Craig Ringer	View Answer on Stackoverflow
Solution 2 - Postgresql	knownasilya	View Answer on Stackoverflow
Solution 3 - Postgresql	Alexis Wilke	View Answer on Stackoverflow

How do I convert a binary pgdump (compressed) to a plain SQL file?

Postgresql Problem Overview

Postgresql Solutions

Solution 1 - Postgresql

Solution 2 - Postgresql

Solution 3 - Postgresql

How to localize the images in Images.xcassets?

scikit-learn cross validation, negative values with mean squared error

Attributions