Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.using the 2.0 beta version I get the following error
* warning: pg_query() [function.pg-query]: Query failed: ERROR: duplicate key violates unique constraint "subscriptions_queue_pkey" in /mounts/max30/home/cath/1stsouth/www/includes/database.pgsql.inc on line 125.
* user warning: query: INSERT INTO subscriptions_queue (uid, name, mail, language, module, field, value, author_uid, send_interval, digest, last_sent, load_function, load_args, is_new) SELECT u.uid, u.name, u.mail, u.language, s.module, s.field, s.value, s.author_uid, s.send_interval, su.digest, su.last_sent, 'subscriptions_content_comment_load', '30', '1' FROM subscriptions s INNER JOIN subscriptions_user su ON s.recipient_uid = su.uid INNER JOIN users u USING(uid) WHERE s.module = 'node' AND s.field = 'nid' AND s.author_uid IN (4, -1) AND s.send_comments = 1 AND s.value = '12' in /mounts/max30/home/cath/1stsouth/www/includes/database.pgsql.inc on line 144.
when trying to reply to a comment in the forum.
Also I tried subscribing to threads and it just seemed to ignore the action also didn't show up when looking at the subscriptions tab in my account, however one of my users has managed to subscribe to a thread, don't know how.
If you need access to the site this can be provided.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | subscriptions.install.pgsql_.patch | 3.34 KB | salvis |
Comments
Comment #1
salvisThank you for the report.
Please apply this patch, disable and uninstall Subscriptions (all Subscriptions modules) and reinstall.
One more thing: You may have to manually delete the two sequences before you can reinstall:
subscriptions_sid_seq
subscriptions_queue_sqid_seq
Comment #2
bfo commenteddon't get error messages any more, however it doesn't email me.
I manually deleted the sequences and put the patch in.
the interface is all there, when I subscribe to a thread now it shows it on my tab in my profile, however not getting mails.
If you want to see then i can provide accounts.
Comment #3
bfo commentedstrange it's working now, i'll investigate further, theres deffinately an issue somewhere but I'll do more prodding and report back.
Comment #4
salvisThanks for the positive feedback on the patch.
Notifications are only sent out by cron, not immediately.
Comment #5
bfo commentedYup I've now worked out whats happening.
There is one issue but it should probably go in as a feature request.
As a test i deleted all my subscriptions reset the the time my subscriptions should be sent (from 1 hour to 3) and then subscribed to some threads.
The threads I had subscribed to before I deleted them stayed at 1 hour notifications where the new ones did go to the 3 hour notification.
Can I suggest that when you delete a subscription it's deleted from the table so that when you resubscribe you get your new notification time.
Do you want me to post this as a seperate feature request?
Comment #6
salvisYes, please — this is completely unrelated to pgsql...
... that is, if you really think this is an issue.
Please provide some more information, too. If you "deleted all your subscriptions", then the {subscriptions} table should be empty. Was it not?
Or are you referring to the {subscriptions_queue} table, i.e. notifications that have already been queued but not yet sent? These queued-but-not-yet-sent notifications would follow the old Send Interval, but any new ones should be queued with the new Send Interval. Is that not what you're seeing?
I'm not sure it's worth the effort to purge the queued-but-not-yet-sent notifications, especially because some notifications may be queued by more than one kind of subscription, and the remaining ones would still fire.
Comment #7
salvisComment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.