Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 214601
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T18:23:24+00:00 2026-05-11T18:23:24+00:00

Current situation: Ubuntu 8.04 server edition (live server) Postgresql 8.3.7 (from standard repositories) Postgis

  • 0

Current situation:

  • Ubuntu 8.04 server edition (live server)
  • Postgresql 8.3.7 (from standard repositories)
  • Postgis 1.3.3 (from standard repositories)
  • GEOS 2.3.4 (from standard repositories)

Problem:

GEOS contains bugs which are fixed in the 3.0 release.
I have encountered these and need to upgrade GEOS/Postgis to include the GEOS fixes.

Where i’m standing now:

On a test machine with nearly identical setup, i removed the postgis-packages and tried to recompile Geos 3.1.0 against Postgis 1.3.5 and Postgresql 8.3.7.

After fixing some linking and path problems this works.

My specific question:

What is the best way to migrate my databases (tables, functions, triggers, gist indexes, data…) from the ‘based on older geos/postgis’ version to the ‘newer’ one?

I’ll try the ‘soft-upgrade’ way described in the documentation but do you think this will work?

What’s the best way to make a full backup of this postgis-enabled database so i can completely restore it on the ‘newer postgis version’ i’m compiling?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-11T18:23:25+00:00Added an answer on May 11, 2026 at 6:23 pm

    I’ll try the ‘soft-upgrade’ way described in the documentation but do you think this will work?

    I don’t know enough about GEOS to say for sure, but it sounds like a good thing to try. From the docs you linked to:

    If a soft upgrade is not possible the script will abort and you will be warned about HARD UPGRADE being required, so do not hesitate to try a soft upgrade first.

    Otherwise, I’d just follow their “hard upgrade” directions, which appear to be functionally equivalent to the usual pg_dump/pg_restore approach used to upgrade to a new major version of PostgreSQL. There’s plenty more information in the Postgres documentation about how to do that; it’s a very safe procedure and, as the official migration method, is extremely well supported.

    One thing you may wish to consider is upgrading to the PostgreSQL 8.4 beta while you’re doing all of this work. It’s beta software, true, but that might be acceptable for your environment, and if it is suitable, then you get the new features of 8.4 plus the ability to do a soft upgrade to 8.4 final (as the on-disk formats are not expected to change after the start of beta).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

The situation: I need to convert our current development environment from Windows XP 32-bit to
I have a fairly standard inheritance situation in my current LINQ-to-SQL project. I have
My current project is in Rails. Coming from a Symfony (PHP) and Django (Python)
Current, I've got a stored procedure that has a main goal of doing a
My current development project has two aspects to it. First, there is a public
My current preferred C++ environment is the free and largely excellent Microsoft Visual Studio
My current view is no, prefer Transact SQL stored procedures because they are a
My current setup.py script works okay, but it installs tvnamer.py (the tool) as tvnamer.py
My current place of employment is currently in a transition, new ownership has taken
My current project uses NUnit for unit tests and to drive UATs written with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.