xep0049/private:153 - pq: there is no unique or exclusion constraint matching the ON CONFLICT specification
Closed this issue · 4 comments
waveletlet commented
Not sure if this is a jackal issue or an I don't understand postgres issue... Here's the log lines from immediately before the error.
🔍 [DBG] session/session:228 - RECV(c2s:default:2): <iq xmlns="jabber:client" type="set" id="2ae1ad12-5611-4eac-aee1-7835099e3d8b" from="waveletlet@my.server/gajim.ITKJ"><query xmlns="jabber:iq:private"><roster xmlns="roster:delimiter">::</roster></query></iq>
ℹ️ [INF] xep0049/private:150 - saving private element. ns: roster:delimiter... (waveletlet/gajim.ITKJ)
💥 [ERR] xep0049/private:153 - pq: there is no unique or exclusion constraint matching the ON CONFLICT specification
Pops up when I restart the server for every user that's online. Not seeing anything strange on the client side.
ortuman commented
hi @waveletlet! 👋
could you please provide a list of active constraints on private_storage postgres table?
waveletlet commented
Does this mean anything to you?
conname | connamespace | contype | condeferrable | condeferred | convalidated | conrelid | contypid | conindid | confrelid | confupdtype | confdeltype | confmatchtype | conislocal | coninhcount | connoinherit | conkey | confkey | conpfeqop | conppeqop | conffeqop | conexclop | conbin | consrc
----------------------+--------------+---------+---------------+-------------+--------------+----------+----------+----------+-----------+-------------+-------------+---------------+------------+-------------+--------------+--------+---------+-----------+-----------+-----------+-----------+--------+--------
private_storage_pkey | 2200 | p | f | f | t | 25183 | 0 | 25191 | 0 | | | | t | 0 | t | {1,2} | | | | | | |
(1 row)
(I used the query from https://dba.stackexchange.com/a/214877, if there's one more appropriate for what you're asking for let me know.)
ortuman commented
👋 Hi @waveletlet!
Current 0.4.11 release should fix the issue. Could you please confirm? Thanks! 🙏
waveletlet commented
Not seeing the error anymore, looks good!