Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Apr 17, 2014 at 02:45:59PM -0400, Joseph Kregloh wrote: > > This will be fixed in the next 9.3 minor release by throwing ane error > for non-existent tablespace directories. > > > > Awesome! I have already upgraded my dev, stage, preprod, and production > environments to 9.3. Ho

Re: [GENERAL] pg_upgrade & tablespaces

> This will be fixed in the next 9.3 minor release by throwing ane error > for non-existent tablespace directores. > > Awesome! I have already upgraded my dev, stage, preprod, and production environments to 9.3. However I do have some snapshots that I can test with. > -- > Bruce Momjian

Re: [GENERAL] pg_upgrade & tablespaces

On Mon, Jan 13, 2014 at 09:17:41AM -0500, Joseph Kregloh wrote: > > > > On Fri, Jan 10, 2014 at 11:53 AM, Adrian Klaver > wrote: > > On 01/10/2014 08:40 AM, Joseph Kregloh wrote: > > Just as a followup to this. The process that I am using to do the > upgrade is as follows:

Re: [GENERAL] pg_upgrade & tablespaces

On Wed, Jan 22, 2014 at 04:33:47PM -0500, Joseph Kregloh wrote: > That is excellent news. I still have 3 more environments to upgrade, our > stage, > pre-prod, and production environments in the next month or so. I would be > willing to test any fix you may have. Thanks. I will let you know when

Re: [GENERAL] pg_upgrade & tablespaces

That is excellent news. I still have 3 more environments to upgrade, our stage, pre-prod, and production environments in the next month or so. I would be willing to test any fix you may have. -Joseph On Tue, Jan 21, 2014 at 7:02 PM, Bruce Momjian wrote: > On Mon, Jan 13, 2014 at 09:23:09AM -05

Re: [GENERAL] pg_upgrade & tablespaces

On Mon, Jan 13, 2014 at 09:23:09AM -0500, Joseph Kregloh wrote: > > > > Right.  I know there were multiple issue with this upgrade, jails > probably being the biggest, but a new one I had never heard is that _if_ > you are placing your tablespaces in the PGDATA directory, and you are

Re: [GENERAL] pg_upgrade & tablespaces

Right. I know there were multiple issue with this upgrade, jails > probably being the biggest, but a new one I had never heard is that _if_ > you are placing your tablespaces in the PGDATA directory, and you are > upgrading from pre-9.2, if you rename the old data directory, you also > need to sta

Re: [GENERAL] pg_upgrade & tablespaces

On Fri, Jan 10, 2014 at 11:53 AM, Adrian Klaver wrote: > On 01/10/2014 08:40 AM, Joseph Kregloh wrote: > >> Just as a followup to this. The process that I am using to do the >> upgrade is as follows: >> >> 1. Install Postgres 9.3 in /opt dir. >> 2. In 9.0 instance update spclocation in pg_tablespa

Re: [GENERAL] pg_upgrade & tablespaces

On 01/11/2014 08:18 AM, Bruce Momjian wrote: On Sat, Jan 11, 2014 at 06:43:16AM -0800, Adrian Klaver wrote: Well the issue seems to be with 9.0. I am not exactly sure where pg_upgrade is pulling its information, but I am guessing from the error message that on the 9.0 side of things it is using

Re: [GENERAL] pg_upgrade & tablespaces

On Sat, Jan 11, 2014 at 06:43:16AM -0800, Adrian Klaver wrote: > >>Well the issue seems to be with 9.0. I am not exactly sure where > >>pg_upgrade is pulling its information, but I am guessing from the > >>error message that on the 9.0 side of things it is using > >>spclocation. In the OPs situatio

Re: [GENERAL] pg_upgrade & tablespaces

On 01/10/2014 06:59 PM, Bruce Momjian wrote: On Fri, Dec 27, 2013 at 04:10:25PM -0800, Adrian Klaver wrote: On 12/27/2013 02:52 PM, Jeff Janes wrote: On Friday, December 27, 2013, Joseph Kregloh wrote: FYI, some testing showed that playing around with spclocation in pg_tablespa

Re: [GENERAL] pg_upgrade & tablespaces

On Fri, Dec 27, 2013 at 04:10:25PM -0800, Adrian Klaver wrote: > On 12/27/2013 02:52 PM, Jeff Janes wrote: > >On Friday, December 27, 2013, Joseph Kregloh wrote: > > > >FYI, some testing showed that playing around with spclocation in > >pg_tablespace is not recommended. > > > > > >

Re: [GENERAL] pg_upgrade & tablespaces

On 01/10/2014 08:40 AM, Joseph Kregloh wrote: Just as a followup to this. The process that I am using to do the upgrade is as follows: 1. Install Postgres 9.3 in /opt dir. 2. In 9.0 instance update spclocation in pg_tablespace. 3. Update the symlinks in the pg_tblspace folder. 4. Move the tables

Re: [GENERAL] pg_upgrade & tablespaces

Just as a followup to this. The process that I am using to do the upgrade is as follows: 1. Install Postgres 9.3 in /opt dir. 2. In 9.0 instance update spclocation in pg_tablespace. 3. Update the symlinks in the pg_tblspace folder. 4. Move the tablespace folders to new location. 5. Run pg_upgrade.

Re: [GENERAL] pg_upgrade & tablespaces

On 12/31/2013 04:03 PM, Joseph Kregloh wrote: On Tue, Dec 31, 2013 at 5:08 PM, Adrian Klaver mailto:adrian.kla...@gmail.com>> wrote: On 12/31/2013 01:31 PM, Joseph Kregloh wrote: ERROR: relation "sys_errors" does not exist LINE 1: SELECT * FROM sys_err

Re: [GENERAL] pg_upgrade & tablespaces

On Tue, Dec 31, 2013 at 5:08 PM, Adrian Klaver wrote: > On 12/31/2013 01:31 PM, Joseph Kregloh wrote: > >> >> ERROR: relation "sys_errors" does not exist >> LINE 1: SELECT * FROM sys_errors ORDER BY created_ts DESC LIMIT >> 100; >> ^ >>

Re: [GENERAL] pg_upgrade & tablespaces

On 12/31/2013 01:31 PM, Joseph Kregloh wrote: ERROR: relation "sys_errors" does not exist LINE 1: SELECT * FROM sys_errors ORDER BY created_ts DESC LIMIT 100; ^ ** Error ** ERROR: relation "sys_errors" does not exi

Re: [GENERAL] pg_upgrade & tablespaces

On 12/31/2013 01:51 PM, Joseph Kregloh wrote: So you have not upgraded the tablespaces. What is important to remember is Postgres uses numbers to keep track of relations. Part of the upgrade process involves changing the numbers that point at relations. By manually

Re: [GENERAL] pg_upgrade & tablespaces

> > So you have not upgraded the tablespaces. What is important to remember is >> Postgres uses numbers to keep track of relations. Part of the upgrade >> process involves changing the numbers that point at relations. By manually >> dropping a 9.0 tablespace into a 9.3 data directory you have broke

Re: [GENERAL] pg_upgrade & tablespaces

On 12/31/2013 01:31 PM, Joseph Kregloh wrote: ERROR: relation "sys_errors" does not exist LINE 1: SELECT * FROM sys_errors ORDER BY created_ts DESC LIMIT 100; ^ ** Error ** ERROR: relation "sys_errors" does not exi

Re: [GENERAL] pg_upgrade & tablespaces

> > >> ERROR: relation "sys_errors" does not exist >> LINE 1: SELECT * FROM sys_errors ORDER BY created_ts DESC LIMIT 100; >>^ >> ** Error ** >> >> ERROR: relation "sys_errors" does not exist >> SQL state: 42P01 >> Character: 15 >> > > sys_errors is a table

Re: [GENERAL] pg_upgrade & tablespaces

On 12/31/2013 12:25 PM, Joseph Kregloh wrote: I did a bit more experimenting today. First test: /opt/bin/pg_upgrade -d /usr/local/pgsql/data -D /usr/local/pgsql_93/data/ -b /usr/local/bin/ -B /opt/bin/ -p 5452 -P 5451 It completes successfully, however I still have the user defined tablespaces

Re: [GENERAL] pg_upgrade & tablespaces

I did a bit more experimenting today. First test: /opt/bin/pg_upgrade -d /usr/local/pgsql/data -D /usr/local/pgsql_93/data/ -b /usr/local/bin/ -B /opt/bin/ -p 5452 -P 5451 It completes successfully, however I still have the user defined tablespaces inside the 9.0 data folder. So I manually moved

Re: [GENERAL] pg_upgrade & tablespaces

On 12/27/2013 02:52 PM, Jeff Janes wrote: On Friday, December 27, 2013, Joseph Kregloh wrote: FYI, some testing showed that playing around with spclocation in pg_tablespace is not recommended. Do you happen to have more information about this? Because it would actually

Re: [GENERAL] pg_upgrade & tablespaces

On Friday, December 27, 2013, Joseph Kregloh wrote: > FYI, some testing showed that playing around with spclocation in >> pg_tablespace is not recommended. > > > Do you happen to have more information about this? Because it would > actually solve all my problems by moving the user created tablespa

Re: [GENERAL] pg_upgrade & tablespaces

On 12/27/2013 01:00 PM, Joseph Kregloh wrote: Postgres is going to /usr/local/pgsql/data/drupal___dbspace/ to look for the 9.0 files instead of /usr/local/pgsql_90/data/__drupal_dbspace/ and is trying to copy them as 9.3 versions into the new default location which has the sa

Re: [GENERAL] pg_upgrade & tablespaces

On 12/27/2013 01:56 PM, Joseph Kregloh wrote: FYI, some testing showed that playing around with spclocation in pg_tablespace is not recommended. Do you happen to have more information about this? Because it would actually solve all my problems by moving the user created tablespaces out

Re: [GENERAL] pg_upgrade & tablespaces

> > FYI, some testing showed that playing around with spclocation in > pg_tablespace is not recommended. Do you happen to have more information about this? Because it would actually solve all my problems by moving the user created tablespaces out of the /data directory. But I would like more info

Re: [GENERAL] pg_upgrade & tablespaces

On 12/27/2013 01:00 PM, Joseph Kregloh wrote: Postgres is going to /usr/local/pgsql/data/drupal___dbspace/ to look for the 9.0 files instead of /usr/local/pgsql_90/data/__drupal_dbspace/ and is trying to copy them as 9.3 versions into the new default location which has the sa

Re: [GENERAL] pg_upgrade & tablespaces

> > > Postgres is going to /usr/local/pgsql/data/drupal_dbspace/ to look for > the 9.0 files instead of /usr/local/pgsql_90/data/drupal_dbspace/ and is > trying to copy them as 9.3 versions into the new default location which has > the same path. Since the new > /usr/local/pgsql/data/drupal_dbspac

Re: [GENERAL] pg_upgrade & tablespaces

On 12/27/2013 06:50 AM, Joseph Kregloh wrote: So how are you moving the 9.0 directory? Just using a mv command like below: mv /usr/local/pgsql/data /usr/local/pgsql_90/data Then I recreated the symlinks in /pg_tbspc to point to the new directory path. Ah, now I see the problem, I think

Re: [GENERAL] pg_upgrade & tablespaces

> > >> So how are you moving the 9.0 directory? > Just using a mv command like below: mv /usr/local/pgsql/data /usr/local/pgsql_90/data Then I recreated the symlinks in /pg_tbspc to point to the new directory path. What does a listing for that directory look like after the move? > [pgsql@postgr

Re: [GENERAL] pg_upgrade & tablespaces

On 12/26/2013 01:06 PM, Joseph Kregloh wrote: Here is the message on --hackers that explains the above: http://www.postgresql.org/__message-id/20130214052952.__ga10...@momjian.us Let me read into this. No

Re: [GENERAL] pg_upgrade & tablespaces

> > Here is the message on --hackers that explains the above: > > http://www.postgresql.org/message-id/20130214052952.ga10...@momjian.us > > Let me read into this. > > >> While the upgrade was successful, I find it unusable and leaving me with >> a lot of manual labor ahead of me. Because it leav

Re: [GENERAL] pg_upgrade & tablespaces

On 12/26/2013 08:31 AM, Joseph Kregloh wrote: As suggested I did a couple more experiments. This time I installed Postgres 9.0 in it's defauls location. I then installed Postgres 9.3 in /opt. Tested that both version booted up and ran independently of each other. First test, Postgres 9.0 just af

Re: [GENERAL] pg_upgrade & tablespaces

As suggested I did a couple more experiments. This time I installed Postgres 9.0 in it's defauls location. I then installed Postgres 9.3 in /opt. Tested that both version booted up and ran independently of each other. First test, Postgres 9.0 just after an initdb, so it's all clean. It completed s

Re: [GENERAL] pg_upgrade & tablespaces

On 12/23/2013 6:50 AM, Joseph Kregloh wrote: Well the original architect started out in the 80s with banking databases they just kept that model without revisiting if it works well or not, that might explain it a little bit. But also given the size of our tables we use the physical disks an

Re: [GENERAL] pg_upgrade & tablespaces

On 12/23/2013 06:45 AM, Joseph Kregloh wrote: And /usr/local/pgsql was re-initdbed with a 9.0 cluster, because previously it was the 9.3 cluster? And you are sure /usr/local/bin has the 9.3 binaries? Personally I would say at this point the relationships between versions

Re: [GENERAL] pg_upgrade & tablespaces

On Fri, Dec 20, 2013 at 7:42 PM, John R Pierce wrote: > On 12/20/2013 4:14 PM, Adrian Klaver wrote: > >> >> Personally I would say at this point the relationships between versions >> are so confused it would seem best to start from scratch. >> > > the 80 tablespaces aren't helping this one bit. >

Re: [GENERAL] pg_upgrade & tablespaces

> > And /usr/local/pgsql was re-initdbed with a 9.0 cluster, because > previously it was the 9.3 cluster? > > And you are sure /usr/local/bin has the 9.3 binaries? > > Personally I would say at this point the relationships between versions > are so confused it would seem best to start from scratch

Re: [GENERAL] pg_upgrade & tablespaces

> [root@postgres-93-upgrade /usr/local/pgsql/data/drupal_dbspace]# ls -la >> /home/jkregloh/pg_data/data/drupal_dbspace/ >> drwx-- 4 pgsql pgsql 4 Oct 20 2011 PG_9.0_201008051 >> > > So that looks like it worked, or am I missing something. > Yes, it works but once it gets to the step whe

Re: [GENERAL] pg_upgrade & tablespaces

On 12/20/2013 4:14 PM, Adrian Klaver wrote: Personally I would say at this point the relationships between versions are so confused it would seem best to start from scratch. the 80 tablespaces aren't helping this one bit. I am really curious what lead to creating that many tablespaces? rem

Re: [GENERAL] pg_upgrade & tablespaces

On 12/20/2013 02:01 PM, Joseph Kregloh wrote: Ah, nothing like taking the dog for walk to clear the mind. Led to a thought. To amend my previous post, instead of using the 9.0 cluster you have been using, why not create a minimal test cluster? In the crawl, walk, run vein, start with a datab

Re: [GENERAL] pg_upgrade & tablespaces

On 12/20/2013 02:01 PM, Joseph Kregloh wrote: [root@postgres-93-upgrade /usr/local/pgsql/data/drupal___dbspace]# ls -la /home/jkregloh/pg_data/data/__drupal_dbspace/ drwx-- 4 pgsql pgsql 4 Oct 20 2011 PG_9.0_201008051 So that looks like it worked,

Re: [GENERAL] pg_upgrade & tablespaces

On 12/20/2013 10:42 AM, Joseph Kregloh wrote: So was your latest attempt where you ended up with a doubled data/ in the two or one jail scenario? The two jails scenario. The two jail scenario is the same as the mounted scenario. Can we see a directory listing for that case? Y

Re: [GENERAL] pg_upgrade & tablespaces

> So was your latest attempt where you ended up with a doubled data/ in the > two or one jail scenario? > > The two jails scenario. The two jail scenario is the same as the mounted scenario. Can we see a directory listing for that case? > > You say in the single jail case you got the same results.

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh wrote: > [pgsql@postgres-93-upgrade ~]$ ls -l > /home/jkregloh/pg_data/data/pg_tblspc/ > lrwxr-xr-x 1 pgsql pgsql41 Dec 19 19:53 11047389 -> > /home/jkregloh/pg_data/data/stats_dbspace > lrwxr-xr-x 1 pgsql pgsql44 Dec 19 19:53 11

Re: [GENERAL] pg_upgrade & tablespaces

On 12/20/2013 07:32 AM, Joseph Kregloh wrote: Case B: pg_upgrade -b /home/jkregloh/pg_bin/ -B /usr/local/bin/ -D /usr/local/pgsql_93/data -d /usr/local/pgsql/data/ -P 5452 -p 5451 In this case, the OLD cluster is in the default location and the new one

Re: [GENERAL] pg_upgrade & tablespaces

On Fri, Dec 20, 2013 at 10:26 AM, Adrian Klaver wrote: > On 12/20/2013 06:54 AM, Joseph Kregloh wrote: > >> >> >> >> On Thu, Dec 19, 2013 at 6:19 PM, Adrian Klaver > > wrote: >> >> On 12/19/2013 01:50 PM, Joseph Kregloh wrote: >> >> On Thu, Dec 19, 2013

Re: [GENERAL] pg_upgrade & tablespaces

On 12/20/2013 06:54 AM, Joseph Kregloh wrote: On Thu, Dec 19, 2013 at 6:19 PM, Adrian Klaver mailto:adrian.kla...@gmail.com>> wrote: On 12/19/2013 01:50 PM, Joseph Kregloh wrote: On Thu, Dec 19, 2013 at 4:14 PM, John R Pierce mailto:pie...@hogranch.com>

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 6:19 PM, Adrian Klaver wrote: > On 12/19/2013 01:50 PM, Joseph Kregloh wrote: > >> On Thu, Dec 19, 2013 at 4:14 PM, John R Pierce > > wrote: >> >> On 12/19/2013 1:06 PM, Joseph Kregloh wrote: >> >> It's easier to keep things segregate

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 01:50 PM, Joseph Kregloh wrote: On Thu, Dec 19, 2013 at 4:14 PM, John R Pierce mailto:pie...@hogranch.com>> wrote: On 12/19/2013 1:06 PM, Joseph Kregloh wrote: It's easier to keep things segregated. It is not anymore different than doing the upgrade in the same

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 4:18 PM, Bruce Momjian wrote: > On Thu, Dec 19, 2013 at 01:08:18PM -0800, Sergey Konoplev wrote: > > On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh > > wrote: > > > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev > wrote: > > >> On Thu, Dec 19, 2013 at 12:27 PM, Josep

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 4:16 PM, Adrian Klaver wrote: > On 12/19/2013 01:06 PM, Joseph Kregloh wrote: > >> It's easier to keep things segregated. It is not anymore different than >> doing the upgrade in the same jail. Which at the end of the day you are >> doing the upgrade in the same jail, becau

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 4:14 PM, John R Pierce wrote: > On 12/19/2013 1:06 PM, Joseph Kregloh wrote: > >> It's easier to keep things segregated. It is not anymore different than >> doing the upgrade in the same jail. Which at the end of the day you are >> doing the upgrade in the same jail, becau

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 1:18 PM, Bruce Momjian wrote: > On Thu, Dec 19, 2013 at 01:08:18PM -0800, Sergey Konoplev wrote: >> On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh >> wrote: >> > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev wrote: >> >> Can you show what ls -l /home/jkregloh/pg_data

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 01:14:15PM -0800, John R Pierce wrote: > On 12/19/2013 1:06 PM, Joseph Kregloh wrote: > >It's easier to keep things segregated. It is not anymore different > >than doing the upgrade in the same jail. Which at the end of the > >day you are doing the upgrade in the same jail,

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 01:08:18PM -0800, Sergey Konoplev wrote: > On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh > wrote: > > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev wrote: > >> On Thu, Dec 19, 2013 at 12:27 PM, Joseph Kregloh > >> wrote: > >> > So what I get from this is that it doe

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 01:06 PM, Joseph Kregloh wrote: It's easier to keep things segregated. It is not anymore different than doing the upgrade in the same jail. Which at the end of the day you are doing the upgrade in the same jail, because at the end of the day pg_upgrade just needs the old data an bin

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 1:06 PM, Joseph Kregloh wrote: It's easier to keep things segregated. It is not anymore different than doing the upgrade in the same jail. Which at the end of the day you are doing the upgrade in the same jail, because at the end of the day pg_upgrade just needs the old data an bi

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh wrote: > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev wrote: >> On Thu, Dec 19, 2013 at 12:27 PM, Joseph Kregloh >> wrote: >> > So what I get from this is that it does create the correct 9.3 files in >> > the >> > new location, however it cann

Re: [GENERAL] pg_upgrade & tablespaces

It's easier to keep things segregated. It is not anymore different than doing the upgrade in the same jail. Which at the end of the day you are doing the upgrade in the same jail, because at the end of the day pg_upgrade just needs the old data an binary to start and create some dump files. But th

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 12:53 PM, Bruce Momjian wrote: Currently I am testing on the development database which is only 100GB with a >same number of tablespaces. I am working on FreeBSD with jails. So one jail >contains 9.0 and the other 9.3. In the 93 jail I mount the data and binary >directories for the

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 11:34:24AM -0500, Joseph Kregloh wrote: > Hello, > > I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade utility. > I > need to use pg_upgrade because my production database is 800GB+ and with over > 80 tablespaces and doing an export from 9.0 and importin

Re: [GENERAL] pg_upgrade & tablespaces

Within the jail it would be: [pgsql@postgres-93-upgrade ~]$ mount sata-data/usr/jails/postgres-93-upgrade on / (zfs, local, nfsv4acls) But I am mounting those directories from the host, which will be: [root@v1 /postgres_data/p3-dev-db-93]# mount -l | grep postgres-93-upgrade sata-data/usr/jails/po

Re: [GENERAL] pg_upgrade & tablespaces

[pgsql@postgres-93-upgrade ~]$ ls -l /home/jkregloh/pg_data/data/pg_tblspc/ lrwxr-xr-x 1 pgsql pgsql41 Dec 19 19:53 11047389 -> /home/jkregloh/pg_data/data/stats_dbspace lrwxr-xr-x 1 pgsql pgsql44 Dec 19 19:53 11047390 -> /home/jkregloh/pg_data/data/stats_indexspace lrwxr-xr-x

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 12:46 PM, Joseph Kregloh wrote: I'm not sure what you mean by that question. When you run the mount command in the jail what does it show? -Joseph -- Adrian Klaver adrian.kla...@gmail.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make chang

Re: [GENERAL] pg_upgrade & tablespaces

On Thu, Dec 19, 2013 at 12:27 PM, Joseph Kregloh wrote: > So what I get from this is that it does create the correct 9.3 files in the > new location, however it cannot copy the relation over because the old data > is in the /home/jkregloh/pg_data/data/drupal_dbspace/ not in > /usr/local/pgsql/data

Re: [GENERAL] pg_upgrade & tablespaces

I'm not sure what you mean by that question. -Joseph On Thu, Dec 19, 2013 at 3:41 PM, Adrian Klaver wrote: > On 12/19/2013 12:27 PM, Joseph Kregloh wrote: > >> Here is the output of my last test run: >> >> > >> So what I get from this is that it does create the correct 9.3 files in >> the new l

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 12:27 PM, Joseph Kregloh wrote: Here is the output of my last test run: So what I get from this is that it does create the correct 9.3 files in the new location, however it cannot copy the relation over because the old data is in the /home/jkregloh/pg_data/data/drupal_dbspace/

Re: [GENERAL] pg_upgrade & tablespaces

Here is the output of my last test run: [pgsql@postgres-93-upgrade ~]$ time pg_upgrade -b /home/jkregloh/pg_bin/ -B /usr/local/bin/ -d /home/jkregloh/pg_data/data -D /usr/local/pgsql/data/ -p 5452 -P 5451 Performing Consistency Checks - Checking cluster versions

Re: [GENERAL] pg_upgrade & tablespaces

Yes, the port numbers are correct. Both instances start by themselves on their own jails. On Thu, Dec 19, 2013 at 11:52 AM, Adrian Klaver wrote: > On 12/19/2013 08:34 AM, Joseph Kregloh wrote: > >> Hello, >> >> I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade >> utility. I ne

Re: [GENERAL] pg_upgrade & tablespaces

On 13-12-19 11:34 AM, Joseph Kregloh wrote: Hello, I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade utility. I need to use pg_upgrade because my production database is 800GB+ and with over 80 tablespaces and doing an export from 9.0 and importing to 9.3 would take at least

Re: [GENERAL] pg_upgrade & tablespaces

On 12/19/2013 08:34 AM, Joseph Kregloh wrote: Hello, I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade utility. I need to use pg_upgrade because my production database is 800GB+ and with over 80 tablespaces and doing an export from 9.0 and importing to 9.3 would take at least

[GENERAL] pg_upgrade & tablespaces

Hello, I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade utility. I need to use pg_upgrade because my production database is 800GB+ and with over 80 tablespaces and doing an export from 9.0 and importing to 9.3 would take at least 2 days. Currently I am testing on the developme