Hi Pavlos
This is my understanding of why you were not able to run the query fast
enough after the vacuum analyze. This is possibly what would have happened:
1. The relation has 5 million expired URLs and 5 thousand non-expired
URLs
2. Assuming that the table only has 5 million and 5 th
On Wed, 31 Jan 2024 at 09:09, Philip Semanchuk
wrote:
> So in your case those 5m rows that you deleted were probably still clogging
> up your table until you ran VACUUM FULL.
It seems more likely to me that the VACUUM removed the rows and just
left empty pages in the table. Since there's no ind
> On Jan 30, 2024, at 4:40 AM, Pavlos Kallis wrote:
>
> Shouldn't VACUUM ANALYZE reclaim the disk space?
Hi Pavlos,
The short answer to this is “no”. That’s an important difference between VACUUM
(also known as “plain” VACUUM) and VACUUM FULL. In some special cases plain
VACUUM can reclaim
On Tue, 2024-01-30 at 11:40 +0200, Pavlos Kallis wrote:
> I have the following table:
>
> CREATE TABLE IF NOT EXISTS public.shortened_url
> (
> id character varying(12) COLLATE pg_catalog."default" NOT NULL,
> created_at timestamp without time zone,
> expires_at timestamp without time
Hi all,
I have the following table:
CREATE TABLE IF NOT EXISTS public.shortened_url
(
id character varying(12) COLLATE pg_catalog."default" NOT NULL,
created_at timestamp without time zone,
expires_at timestamp without time zone,
url text COLLATE pg_catalog."default" NOT NULL,
