| From: | Rama Krishnan <raghuldrag(at)gmail(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Need a depth information about bloat |
| Date: | 2020-08-10 04:19:51 |
| Message-ID: | CAJWX+ENZBs4Swr3DoZqr-k414LM8A4oO+4_xU6SUL8NsJn_Chw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thank you for the clarification brother ππ
On Mon, 10 Aug, 2020, 09:47 Rob Sargent, <robjsargent(at)gmail(dot)com> wrote:
>
>
> > On Aug 9, 2020, at 9:01 PM, Rama Krishnan <raghuldrag(at)gmail(dot)com> wrote:
> >
> > ο»Ώ
> > Hi Mentors,
> >
> >
> > I am searching for an understanding of bloat in PostgreSQL
> >
> > What is bloat?
> >
> > How does it work?
> >
> > What is the use of bloat?
> >
> > Limitations of bloat?
> >
> > Thanks
> >
> > Rama Krishnan
> Bloat is not a feature of postgreSQL, itβs a consequence. It has no
> redeeming value.
> Updates to tuples generally cause a new tuples to be constructed and the
> original to be marked as disposable. It is the job of the vacuum process to
> rid the table of this record. Until this happens the marked record as part
> of the bloat for that table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rama Krishnan | 2020-08-10 04:20:30 | Re: Need a depth information about bloat |
| Previous Message | Rob Sargent | 2020-08-10 04:17:53 | Re: Need a depth information about bloat |