Bug #95843
closed
Typo3 Install Fail with PostgreSQL
0%
Description
Postgresql 9.2
- Attempt to install Typo3 11.5.0-11.5.2 (via tar.gz)
- Installing TYPO3 CMS 4 / 5 - 80% Complete
Create Administrative User & Specify Site Name
Use this account to log into the backend of your site.
The password you provide for this account is also used to access the Install Tool.
On this page you can also set a name for your new website.
Database query failed!
Query: CREATE INDEX "uid_foreign" ON sys_category_record_mm ("uid_foreign") Error: SQLSTATE[42P07]: Duplicate table: 7 ERROR: relation "uid_foreign" already exists
it is not possible to continue.
If i reload with F5, it shows "100% Complete" but there is no data in the database, only the structure.
INDEX "uid_foreign" already exists for sys_file_reference.
Files
Updated by Christian Kuhn about 3 years ago
- Status changed from New to Needs Feedback
Could you re-try with younger postgres versions, for instance >=10 please? 9.2 is seriously old and end-of-life since 2017 in upstream. Our installer acceptance test uses postgres 10, too and the test is fine with it.
Updated by Raoul STANISLAS about 3 years ago
Christian Kuhn wrote in #note-1:
Could you re-try with younger postgres versions, for instance >=10 please? 9.2 is seriously old and end-of-life since 2017 in upstream. Our installer acceptance test uses postgres 10, too and the test is fine with it.
It is not possible to upgrade the Postgresql version.
Since no version is specified on https://get.typo3.org/version/11 I didn't think this would be a problem.
Updated by Raoul STANISLAS over 2 years ago
Raoul STANISLAS wrote in #note-2:
Christian Kuhn wrote in #note-1:
Could you re-try with younger postgres versions, for instance >=10 please? 9.2 is seriously old and end-of-life since 2017 in upstream. Our installer acceptance test uses postgres 10, too and the test is fine with it.
It is not possible to upgrade the Postgresql version.
Since no version is specified on https://get.typo3.org/version/11 I didn't think this would be a problem.
Yes thanks ! it works on new environment with Postgresql 14
Updated by Riccardo De Contardi about 2 years ago
@Raoul STANISLAS thank you for your feedback;
May I ask you if you think that this issue can be closed? Or is there still work to be done here?
Thank you!
Updated by Riccardo De Contardi almost 2 years ago
- Status changed from Needs Feedback to Closed
No feedback since more than 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.
Thank you and best regards