eg_db_config needs to recognize Postgres 9.3

Bug #1290499 reported by Remington Steed on 2014-03-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
High
Unassigned

Bug Description

Evergreen Master
PostgreSQL 9.3.0

When building the database using Postgres 9.3, Evergreen displays the following message:

********************************************************************************
* There is no configuration for full text search config, for the database *
* version you have installed ($a). If you're not really sure why, you should *
* proabably press 'Control-C' now, and abort. To continue using the latest *
* available version ($b), press enter. For assistance, please email *
* <email address hidden> or join #Evergreen on the *
* freenode IRC network. *
********************************************************************************

The script that produces this message (Pg/build-db.sh) is looking for the following config file:

Open-ILS/src/sql/Pg/000.english.pg93.fts-config.sql

Using the existing file for "pg91" builds the database correctly. We should either create the missing file or create a sym link to the working "pg91" file.

Revision history for this message
Remington Steed (rjs7) wrote :

Here's my very simple branch. It just adds the symbolic link, which follows the example of the 9.2 config file.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/rsteed/lp1290499_pg93_config_symlink

working/user/rsteed/lp1290499_pg93_config_symlink

Remington Steed (rjs7) on 2014-03-10
tags: added: pullrequest
Dan Wells (dbw2) on 2014-03-10
Changed in evergreen:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Dan Scott (denials) wrote : Re: [Bug 1290499] Re: eg_db_config needs to recognize Postgres 9.3

Can we make this bug depend on the currently open 2.6 rc-blocker bugs that
are caused by incompatibilities with postgresql 9.3?

I would rather not let someone install Evergreen on 9.3 when we know it
will silently/subtly fail. After those blocker bugs are merged, then would
be the time to merge this one.

Revision history for this message
Dan Wells (dbw2) wrote :

I definitely agree with Dan's point above. Glad to see this ready to go when the times comes.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers