You don't need "-t history" on the psql part. It doesn't do what you think
it does, and it's reading the next part ("history") as the database name.
try:
pg_dump -h -U postgres -t history DATABASENAME | psql -h
hostname2 -U postgres DATABASENAME > db.sql
Derrick
On Tue, Sep 20, 2011 at 11:57
On Wed, Mar 16, 2011 at 5:56 PM, Kevin Grittner wrote:
> there is a feature to probe the end of an index's range in
> situations where data skew was often causing less than optimal plans
> to be chosen.
>
Was this introduced in 9.0 or was it earlier? My company hasn't introduced
integrated supp
Oh, I'm using 8.2
On Wed, Mar 16, 2011 at 3:40 PM, Derrick Rice wrote:
> Greetings.
>
> I recently ran into a problem with a planner opting for a sequential scan
> rather than a bitmap heap scan because the stats suggested that my delete
> query was going to affect 33% of t
Greetings.
I recently ran into a problem with a planner opting for a sequential scan
rather than a bitmap heap scan because the stats suggested that my delete
query was going to affect 33% of the rows, rather than the 1% it really
was. I was able to follow the planner's logic and came to the real
