We shouldn't have a problem with using pg_upgrade with the hard link option to upgrade from postgreSQL 9.1.6 after I get the spatial component upgraded to postgis 2.1, then straight to postgreSQL 9.3, Right? thanks
Original Message
Subject: Re: [BUGS] Installing/Upgrading Postgr
Bruce, Proposed Steps. Do they look feasible?1.) pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f "/somepath/testdb.backup" testdb2.) CREATE DATABASE newdb TEMPLATE=template_postgis;3.) perl ../postgis-postgres/postgis-2.1.1/utils/postgis_restore.pl "/somepath/testdb.backup" | psql -h localhos
1.) During our prior upgrade process we used pg_upgrade to move from pg 8.4.3 to 9.1.6 using the hard links install option, we also have our data spread across disk storage mediums; fiber, nas. Are there any known issues, bugs with using pg_upgrade to move from 9.1.6 to pg 9.3?2.) We also have to s
Thanks Jaime for your feedback, I did add an index on SARS_ACTS_RUN.ALGORITHM column but it didn't improve the run time. The planner just changed the "Filter:" to an "Index Scan:" improving the cost of the Seq Scan on the sars_acts_run table, but the overall run time remained the same. It seems lik
The SARS_ACTS table currently has 37,115,515 rowswe have indexed: idx_sars_acts_acts_run_id ON SARS_ACTS USING btree (sars_run_id)we have pk constraint on the SARS_ACTS_RUN table; sars_acts_run_pkey PRIMARY KEY (id )serverdb=# explain select count(*) as y0_ from SARS_ACTS this_ inner join SARS_ACTS
Hi John,
The SQL query should be: select count(*) from dna_strands where cid = 1;
I just realize don't think this is not going to work. if for the sake of argument that cid = 1 is much more likely be be found in a more recent partition, any inverse search mechanism in the planner will find tha
Sorry, Is this visible?
We are having performance related problems on one of our big data Partition tables. The table is partitioned by date and the partitions are organized from Jan 2003 thru Dec 2013. We have 268 child partitions associated with the Parent table, and we have constraint_exclusi
We are having performance related problems on one of our big data Partition tables. The table is partitioned by date and the partitions are organized from Jan 2003 thru Dec 2013. We have 268 child partitions associated with the Parent table, and we have constraint_exclusion=partition set.
The ex
Thanks Kevin & Bruce for your replies,
It looks like this script deletes all of the data file directories (and the data files) from the postgres 8.4.3 instance. Since we used the "-k" option, which calls for hard links rather than copying files to the new cluster, wouldn't this be deleting the f
Does anyone know, what the names/location of the pg_upgrade cleanup scripts? We upgraded from 8.4.3 to 9.1.6thanks Original Message Subject: Re: [BUGS] Excessive space allocations in Postgresql 9.1.6system files causing the file system to run out of space.From: Kevin Grittner
Does anyone know, what the names/location of the pg_upgrade cleanup scripts? We upgraded from 8.4.3 to 9.1.6 on linux
thanks
Original Message Subject: Re: [BUGS] Excessive space allocations in Postgresql 9.1.6system files causing the file system to run out of space.From: Kev
Hi Kevin,
Do you know the name that was given to the cleanup script?
thanks
Original Message Subject: Re: [BUGS] Excessive space allocations in Postgresql 9.1.6system files causing the file system to run out of space.From: Kevin Grittner Date: Fri, March 0
Not sure why my emails replies went out in HTML format, I'm re-sending the email trail to date. Thanks Andres for pointing this out.
Freddie
- Most recent Reply ---
We did use pg_upgrade with the hard link option. We are not sure if we ran the cleanup script. Not sure which script you
We did use pg_upgrade with the hard link option. We are not sure if we ran the cleanup script.
Not sure which script you are referring to? Is that script the one that removes the stuff in the source bin directory?
We did the pg_largeobject.sql script, as we were instructed by the pg_upgrade pr
On tuesday, February 26, 2013, Freddie Burgess wrote:
We have a Postgres database that was recently upgraded from 8.4.3 to 9.1.6. We have noticed unusual growth in the data files and generated a script to perform the following actions.1. Query pg_class for all records2. Generate a file listing o
15 matches
Mail list logo