We couldn't drop the table in the normal setup because of the wraparound
protection measures. Specifically: "ERROR: database is not accepting
commands to avoid wraparound data loss in database"
We also tried vacuuming the table. The vacuum didn't generate an error (the
wraparound warning was prin
Ricky Ramirez writes:
> Hello,
>
> We have run into a strange situation with our database. A temporary
> table was created some time ago and that session has since died.
> However, the temporary table stuck around. It's been around long
> enough that postgres stopped accepting writes to prevent
>
Forgive me for forgetting the basics PG 11.2 on Ubuntu Bionic, amd64. No
extensions enabled.
On Mon, May 4, 2020 at 4:54 PM Tom Lane wrote:
> Ricky Ramirez writes:
> > We have run into a strange situation with our database. A temporary table
> > was created some time ago and that session has si
Ricky Ramirez writes:
> We have run into a strange situation with our database. A temporary table
> was created some time ago and that session has since died. However, the
> temporary table stuck around. It's been around long enough that postgres
> stopped accepting writes to prevent transaction I
Hello,
We have run into a strange situation with our database. A temporary table
was created some time ago and that session has since died. However, the
temporary table stuck around. It's been around long enough that postgres
stopped accepting writes to prevent transaction ID wraparound. Problem i
