| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
| Cc: | salah jubeh <s_jubeh(at)yahoo(dot)com>, pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: bloating index, pg_restore |
| Date: | 2013-03-28 04:08:19 |
| Message-ID: | 14576.1364443699@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> writes:
> On Wed, Mar 27, 2013 at 9:56 AM, salah jubeh <s_jubeh(at)yahoo(dot)com> wrote:
>> I have a database which is bloated because of vacuum full, so you find
>> indexes bigger than the table itself.
> Table can not be bloated because of vacuum full, it removes bloat from
> the table and its indexes.
Um, well, that depends a lot on which PG version the OP is running
(which he didn't say). The pre-9.0 implementation of VACUUM FULL
was notorious for creating index bloat, because it shuffled heap
entries around to compact heap space, but created an additional
index entry for each such heap-tuple motion.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Izmailov | 2013-03-28 05:03:01 | Re: [HACKERS] money with 4 digits after dot |
| Previous Message | Sergey Konoplev | 2013-03-28 03:49:23 | Re: bloating index, pg_restore |