Add note about DISABLE_SERVER_SIDE_CURSORS when using pgpool or pgbouncer #9073

Closed
opened 2025-12-29 20:45:05 +01:00 by adam · 2 comments
Owner

Originally created by @abhi1693 on GitHub (Jan 10, 2024).

Change Type

Addition

Area

Installation/upgrade

Proposed Changes

There was an issue that was raised a while back when migrations failed in v3.6. This was due to the usage of either pgpool or pgbouncer in the setup. Ref: https://github.com/netbox-community/netbox/discussions/13994

The failure was due to the use of Queryset().iterator in the migrations which is not compatible with these softwares.

As per Django docs, when either of such sfotwares are used, DISABLE_SERVER_SIDE_CURSORS should be set to True, see: https://docs.djangoproject.com/en/5.0/ref/databases/#server-side-cursors

I'm suggesting to add a note in installation process to point this out for versions greater than v3.6.

Originally created by @abhi1693 on GitHub (Jan 10, 2024). ### Change Type Addition ### Area Installation/upgrade ### Proposed Changes There was an issue that was raised a while back when migrations failed in v3.6. This was due to the usage of either `pgpool` or `pgbouncer` in the setup. Ref: https://github.com/netbox-community/netbox/discussions/13994 The failure was due to the use of `Queryset().iterator` in the migrations which is not compatible with these softwares. As per Django docs, when either of such sfotwares are used, `DISABLE_SERVER_SIDE_CURSORS` should be set to `True`, see: https://docs.djangoproject.com/en/5.0/ref/databases/#server-side-cursors I'm suggesting to add a note in installation process to point this out for versions greater than v3.6.
adam added the type: documentationstatus: needs ownerpending closure labels 2025-12-29 20:45:05 +01:00
adam closed this issue 2025-12-29 20:45:05 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (May 15, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 15, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jun 15, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 15, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9073