BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: https://bugs.horde.org/ticket/14878
------------------------------------------------------------------------------
Ticket | 14878
Erstellt Von | [email protected]
Zusammenfassung | Sequence reset incompatible with PostgreSQL 10+
Warteschlange | Horde Base
Version | 5.2.20
Typ | Bug
Status | Unconfirmed
Priorität | 2. Medium
Milestone |
Patch |
Zuständige |
------------------------------------------------------------------------------
[email protected] (2018-11-26 11:16) hat geschrieben:
After upgrading the database from PostgreSQL 9.6 to 11 certain
operations fail when trying to reset a sequence.
Example to reproduce:
Create a new event in Kronolith raises an error (see attached log).
After refreshing the page the event is created successfully.
Cause:
Method "resetPkSequence" in file
"pear/Horde/Db/Adapter/Postgresql/Schema.php" executes the following
SQL:
SELECT setval(%s, (SELECT COALESCE(MAX(%s) + (SELECT increment_by FROM
%s), (SELECT min_value FROM %s)) FROM %s), false)
Sequence column "increment_by" is no longer available in PostgreSQL 10
and above.
[email protected] (2018-11-26 11:16) hat hochgeladen: horde-seq-pg11.log
https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=horde-seq-pg11.log&ticket=14878&fn=%2Fhorde-seq-pg11.log
--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.