On 2023-03-16 20:24:49 +0100, Laurenz Albe wrote:
> On Thu, 2023-03-16 at 13:20 +, Dolan, Sean wrote:
> > I messed up and confused issues. The error is :
> > ERROR: Could not extend pg_tblspc/16555/PG_13_20200// No space
> > left on device
> > HINT: Check free disk space
> >
> >
On Thu, 2023-03-16 at 13:20 +, Dolan, Sean wrote:
> I messed up and confused issues. The error is :
> ERROR: Could not extend pg_tblspc/16555/PG_13_20200// No space left
> on device
> HINT: Check free disk space
>
> So the schema is "full" and the offender is this one table.
> I
quot;No Free extents", table using all allocated space but
no rows!
On Thu, 2023-03-16 at 01:58 +, Dolan, Sean wrote:
> Environment: PostGres 13 on RedHat 7.9.
>
> I am using logical replication (publisher/subscriber) between two
> databases and there are times whe
On Thu, 2023-03-16 at 01:58 +, Dolan, Sean wrote:
> Environment: PostGres 13 on RedHat 7.9.
>
> I am using logical replication (publisher/subscriber) between two databases
> and there
> are times where one of our schemas gets to 100% of allocated space (No Free
> Extents).
> I went into
Environment: PostGres 13 on RedHat 7.9.
I am using logical replication (publisher/subscriber) between two databases and
there are times where one of our schemas gets to 100% of allocated space (No
Free Extents). I went into the schema and did a \dt+ to see the amount of
size being used and I
