?
avatar richard67
richard67
17 Sep 2019

Steps to reproduce the issue

  1. Make a new, clean installation of current 4.0-dev using an empty PostgreSQL database and note the database prefix used for this installation.
  2. After successful installation, delete configuration.php and install again into the same database, using the same database prefix.

Expected result

At the 2nd installation, previously existing tables should be backed up by renaming them.

Actual result

Installation fails, error alert shown:

snap-3

In PostgreSQL log file:

2019-09-17 20:11:34.151 CEST [6537] jdb1adm@joomladb1 ERROR:  relation "j4ux0_finder_terms_idx_term" already exists
2019-09-17 20:11:34.151 CEST [6537] jdb1adm@joomladb1 STATEMENT:  ALTER INDEX j4ux0_finder_terms_idx_term RENAME TO j4ux0_finder_terms_idx_term

System information (as much as possible)

PHP 7.2
PostgreSQL database version 10.10

Additional comments

Thanks @alikon for reporting this issue. I can confirm it.

avatar richard67 richard67 - open - 17 Sep 2019
avatar joomla-cms-bot joomla-cms-bot - change - 17 Sep 2019
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 17 Sep 2019
avatar richard67 richard67 - change - 17 Sep 2019
Category Installation Postgresql
avatar richard67 richard67 - change - 17 Sep 2019
Build staging 4.0-dev
avatar alikon
alikon - comment - 17 Sep 2019

just let me add this discussion for better reference #18835

avatar brianteeman
brianteeman - comment - 17 Sep 2019

sounds like a simple bug and nothing to do with that issue

avatar brianteeman
brianteeman - comment - 17 Sep 2019

I am trying to test it but I cant get the joomla installer to see my newly installed pgsql 11.5. its running because I can access it through the shell/cli

will have to try again later

avatar richard67
richard67 - comment - 17 Sep 2019

Well the main difference between MySQL and PostgreSQL here is that on PostgreSQL it needs not only to rename the tables but also the indexes, because index names are preceeded by the table names. And there happens the error. According to the log the new name is the same name as the old name when renaming the index. I am looking for it but have to go sleep soon, work tomorrow.

avatar richard67
richard67 - comment - 17 Sep 2019

Table rename happens in database framework, in case of PostgreSQL driver including the indexes ... I have to further check code there.
Update: Code looks ok there ... so it needs deeper digging.

avatar brianteeman
brianteeman - comment - 18 Sep 2019

I have postgres:pdo working now.

avatar brianteeman
brianteeman - comment - 18 Sep 2019

Fixed it - pr incoming

Its a sql error

avatar richard67
richard67 - comment - 18 Sep 2019

Closing as having PR #26351 .

avatar richard67 richard67 - change - 18 Sep 2019
Status New Closed
Closed_Date 0000-00-00 00:00:00 2019-09-18 12:59:19
Closed_By richard67
avatar richard67 richard67 - close - 18 Sep 2019

Add a Comment

Login with GitHub to post a comment