Problems with import/export and categorycombos

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:
pg_restore: [archiver] unsupported version (1.11) in file header

Thats wicked! I’ll try and push everything back to 8.3 again. Any of you postgres experts got an idea about 8.3/8.4 compatibility?

Regards
Bob

···

2009/12/14 Bob Jolliffe bobjolliffe@gmail.com

Lars I’ll look at this this evening. I think I remember its a bug in categorycategorycombo association convertor.

2009/12/14 Ola Hodne Titlestad olatitle@gmail.com

Hi guys,

I’m working on the SL databases, trying to clean up the exisiting datasets and come up with a new db for 2010

and came across some problems with import/export seems none of my catcombo-category relations came across with DXF…

The first thing I did was to clean up all the duplicate categorytions being used across different categories.
That should be fine now.

Then I exported all the metadata over to a new database and then it seems some of the information did not come across in the DXF.

I have attached the dxf file and the new database (after the import).

Ola

That’s weird, I recently got a pg backup from Ola which I could not restore because I was running 8.3 and he 8.4… (I upgraded and it worked).

···

On Mon, Dec 14, 2009 at 6:35 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:
pg_restore: [archiver] unsupported version (1.11) in file header

Thats wicked! I’ll try and push everything back to 8.3 again. Any of you postgres experts got an idea about 8.3/8.4 compatibility?

Postgres is sensitive to minor version changes.

pg_restore --ignore-version will solve your problems in all likelihood.

The command line is you friend. Do not fear it. pg_restore --help
would have saved a few CPU cycles. :slight_smile:

Regards,
Jason

···

On 12/14/09, Lars Helge Øverland <larshelge@gmail.com> wrote:

On Mon, Dec 14, 2009 at 6:35 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to
ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:
pg_restore: [archiver] unsupported version (1.11) in file header

Thats wicked! I'll try and push everything back to 8.3 again. Any of you
postgres experts got an idea about 8.3/8.4 compatibility?

That's weird, I recently got a pg backup from Ola which I could not restore
because I was running 8.3 and he 8.4... (I upgraded and it worked).

I have had the same problem as Lars (I dumped on my laptop’s 8.4 and couldn’t restore on the server’s 8.3). But I thought the other way should work - apparently not. You dont in fact need to change the whole server, it is only the pg_restore that needs replacement. I solved my own problem by accessing the server from the PgAdmin on my laptop, thus using the 8.4 restore to restore to add data to the 8.3 database (at least that’s what I think I did, it’s been some time…)

Knut

···

2009/12/14 Lars Helge Øverland larshelge@gmail.com

On Mon, Dec 14, 2009 at 6:35 PM, Bob Jolliffe bobjolliffe@gmail.com wrote:

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:
pg_restore: [archiver] unsupported version (1.11) in file header

Thats wicked! I’ll try and push everything back to 8.3 again. Any of you postgres experts got an idea about 8.3/8.4 compatibility?

That’s weird, I recently got a pg backup from Ola which I could not restore because I was running 8.3 and he 8.4… (I upgraded and it worked).


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Cheers,
Knut Staring

This is really not a good idea. There can be changes between minor
versions, this is why Postgres is picky. Using a different version of
pg_restore with a different Postgres database could be a recipe for
disaster.

Having said this. DHIS utilizes essentially no custom aspects of
postgres, so differences between minor versionf of postgres "should"
present no issues, but there is no guarentee.

As usual, unless there is a reason to upgrade a production database
package, it probably is not a good idea to do so, just because a new
one has been released unless it is thoroughly tested.

···

On 12/14/09, Knut Staring <knutst@gmail.com> wrote:

I have had the same problem as Lars (I dumped on my laptop's 8.4 and
couldn't restore on the server's 8.3). But I thought the other way should
work - apparently not. You dont in fact need to change the whole server, it
is only the pg_restore that needs replacement. I solved my own problem by
accessing the server from the PgAdmin on my laptop, thus using the 8.4
restore to restore to add data to the 8.3 database (at least that's what I
think I did, it's been some time...)

Knut

2009/12/14 Lars Helge Øverland <larshelge@gmail.com>

On Mon, Dec 14, 2009 at 6:35 PM, Bob Jolliffe >> <bobjolliffe@gmail.com>wrote:

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to
ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:
pg_restore: [archiver] unsupported version (1.11) in file header

Thats wicked! I'll try and push everything back to 8.3 again. Any of
you
postgres experts got an idea about 8.3/8.4 compatibility?

That's weird, I recently got a pg backup from Ola which I could not
restore
because I was running 8.3 and he 8.4... (I upgraded and it worked).

_______________________________________________
Mailing list: DHIS 2 developers in Launchpad
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : DHIS 2 developers in Launchpad
More help : ListHelp - Launchpad Help

--
Cheers,
Knut Staring

This is really not a good idea. There can be changes between minor

versions, this is why Postgres is picky. Using a different version of

pg_restore with a different Postgres database could be a recipe for
disaster.

Having said this. DHIS utilizes essentially no custom aspects of

postgres, so differences between minor versionf of postgres “should”
present no issues, but there is no guarentee.

Agree that it is not ideal, but it did work fine in this case.

As usual, unless there is a reason to upgrade a production database

package, it probably is not a good idea to do so, just because a new

one has been released unless it is thoroughly tested.

Yeah, but in general people will always install the newest version, just like Bob inadvertently had, and I don’t think it makes sense for us to require everyone to use 8.3, for the reasons you state above (we dont use any specific features, and --ignore-versions seems to work).

Knut

···

2009/12/14 Jason Pickering jason.p.pickering@gmail.com

On 12/14/09, Knut Staring knutst@gmail.com wrote:

I have had the same problem as Lars (I dumped on my laptop’s 8.4 and

couldn’t restore on the server’s 8.3). But I thought the other way should

work - apparently not. You dont in fact need to change the whole server, it

is only the pg_restore that needs replacement. I solved my own problem by

accessing the server from the PgAdmin on my laptop, thus using the 8.4

restore to restore to add data to the 8.3 database (at least that’s what I

think I did, it’s been some time…)

Knut

2009/12/14 Lars Helge Øverland larshelge@gmail.com

On Mon, Dec 14, 2009 at 6:35 PM, Bob Jolliffe > > >> bobjolliffe@gmail.comwrote:

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to

ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:

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

Thats wicked! I’ll try and push everything back to 8.3 again. Any of

you

postgres experts got an idea about 8.3/8.4 compatibility?

That’s weird, I recently got a pg backup from Ola which I could not

restore

because I was running 8.3 and he 8.4… (I upgraded and it worked).


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Cheers,

Knut Staring


Cheers,
Knut Staring

OK it was Ola not me! The dump file is v8.4.1. Now imported into 8.4.1. Good I’m not a production database admin :slight_smile:

···

2009/12/14 Bob Jolliffe bobjolliffe@gmail.com

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:

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

Thats wicked! I’ll try and push everything back to 8.3 again. Any of you postgres experts got an idea about 8.3/8.4 compatibility?

Regards
Bob

2009/12/14 Bob Jolliffe bobjolliffe@gmail.com

Lars I’ll look at this this evening. I think I remember its a bug in categorycategorycombo association convertor.

2009/12/14 Ola Hodne Titlestad olatitle@gmail.com

Hi guys,

I’m working on the SL databases, trying to clean up the exisiting datasets and come up with a new db for 2010

and came across some problems with import/export seems none of my catcombo-category relations came across with DXF…

The first thing I did was to clean up all the duplicate categorytions being used across different categories.
That should be fine now.

Then I exported all the metadata over to a new database and then it seems some of the information did not come across in the DXF.

I have attached the dxf file and the new database (after the import).

Ola

Postgres is very picky about versions but generally dumps are
compatible between versions, at least in terms of dhis which utilizes
no custom postgres functionality. Google will tell you how to coerce
postgres into accepting dumps from different versions. Jason

···

On 12/14/09, Lars Helge Øverland <larshelge@gmail.com> wrote:

On Mon, Dec 14, 2009 at 6:35 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:

I seem to have inadvertently upgraded to postgres 8.4 when upgrading to
ubuntu karmic. Now it seems I cannot read the 8.3 dumpfile:
pg_restore: [archiver] unsupported version (1.11) in file header

Thats wicked! I'll try and push everything back to 8.3 again. Any of you
postgres experts got an idea about 8.3/8.4 compatibility?

That's weird, I recently got a pg backup from Ola which I could not restore
because I was running 8.3 and he 8.4... (I upgraded and it worked).

--
Sent from my mobile device