starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add a note to invalidate cache after performing DB dump #2962

New Issue
Closed
opened 2025-12-29 18:24:05 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:24:05 +01:00
Owner
Copy Link

Originally created by @bdlamprecht on GitHub (Oct 18, 2019).

Change Type

[X] Addition
[ ] Correction
[ ] Deprecation
[ ] Cleanup (formatting, typos, etc.)

Proposed Changes

Add some type of note regarding the need to invalidate the cache when migrating the Postgres DB between different machines.

I'll open a PR soon that addresses this fairly simple change.

Originally created by @bdlamprecht on GitHub (Oct 18, 2019). ### Change Type [X] Addition [ ] Correction [ ] Deprecation [ ] Cleanup (formatting, typos, etc.) <!-- Describe the proposed change(s). --> ### Proposed Changes Add some type of note regarding the need to invalidate the cache when migrating the Postgres DB between different machines. I'll open a PR soon that addresses this fairly simple change.
adam added the status: acceptedtype: documentation labels 2025-12-29 18:24:05 +01:00
adam closed this issue 2025-12-29 18:24:06 +01:00
adam commented 2025-12-29 18:24:06 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Oct 24, 2019):

Could you elaborate on:

  1. the scenario you are hinting at (what is migrated? Only the app, the cache or the DB is moved?)
  2. why invalidation is needed in this scenario, what problem does it solve?
@sdktr commented on GitHub (Oct 24, 2019): Could you elaborate on: 1) the scenario you are hinting at (what is migrated? Only the app, the cache or the DB is moved?) 2) why invalidation is needed in this scenario, what problem does it solve?
adam commented 2025-12-29 18:24:06 +01:00
Author
Owner
Copy Link

@bdlamprecht commented on GitHub (Oct 24, 2019):

When migrating the data from one instance of NetBox to another separate server, without performing this command, it takes 10+ minutes for the sites or devices to appear on the appropriate webpage, even though they actually are there.

So no, it is not the end of the world, but just something to keep in mind.

@bdlamprecht commented on GitHub (Oct 24, 2019): When migrating the data from one instance of NetBox to another **separate** server, without performing this command, it takes 10+ minutes for the `sites` or `devices` to appear on the appropriate webpage, even though they _actually_ are there. So no, it is not the end of the world, but just something to keep in mind.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2962
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?