Skip to content

[bot] fix lint errors #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[bot] fix lint errors #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ontent/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ rename to table_name;

---

### Cause 3: table or function actually does not exist
### Cause 3: Table or function actually does not exist

One may have never made the table or dropped it deliberately or accidentally. This can be quickly checked with the following query:

Expand Down
6 changes: 3 additions & 3 deletions ...ontent/troubleshooting/why-are-there-gaps-in-my-postgres-id-sequence-Frifus.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ It's also important to understand the distinction that sequences guarantee **uni

If you don't know the name of your sequence, it's often formed based on a standard naming convention: table_name_id_seq, where table_name is the name of your table and id is the name of your serial column.

### Common Reasons for Gaps in Sequences
### Common reasons for gaps in sequences

1. Rollbacks
One of the most common reasons for a gap is the rollback of a transaction. If you initiate a transaction that includes an insert operation, the sequence responsible for generating the ID for the new row increments. If, for any reason, the transaction doesn't complete successfully—perhaps due to a constraint violation or a deliberate decision to rollback—the insert operation is undone, but the sequence value used is not returned or reused. The documentation explains that as well:
Expand All @@ -35,7 +35,7 @@ If you don't know the name of your sequence, it's often formed based on a standa
4. Upserts
When an upsert is executed, it can still increase the sequence even if it is set to do nothing on conflicts

### Checking for Gaps
### Checking for gaps

To check for gaps in the sequence of IDs in a PostgreSQL table, you can use a SQL query that compares the sequence of IDs to a generated series of numbers that spans the same range:

Expand All @@ -51,7 +51,7 @@ WHERE

This query should help you pinpoint where gaps exist.

### Encountering Errors and Adjusting Sequences
### Encountering errors and adjusting sequences

In operations involving sequences, you might encounter an error message such as:

Expand Down