#6325: Useless Index updates
On 12/04/2011 08:54 PM, dmigow...@ikoffice.de wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6325
> Logged by: Daniel Migowski
> Email address: dmigow...@ikoffice.de
> PostgreSQL version: 8.3.16
> Oper
On 12/05/2011 08:16 AM, Andreas Karlsson wrote:
On 2011-12-04 15:02, Craig Ringer wrote:
- The index isn't always updated. Check out HOT (introduced in 8.4, the
release after your current one) which reduces unnecessary index
updates in cases where the old and new row can fit on the same
heap pag
On 2011-12-04 15:02, Craig Ringer wrote:
- The index isn't always updated. Check out HOT (introduced in 8.4, the
release after your current one) which reduces unnecessary index
updates in cases where the old and new row can fit on the same
heap page.
Minor correction: HOT was introduced in 8.3.
On Sun, Dec 04, 2011 at 12:54:25PM +, dmigow...@ikoffice.de wrote:
> It seems that an update to a row in a table always removes the element from
> an index and adds it again. Wouldn't it be faster to check for equality of
> the index parameters in the OLD and NEW record first?
http://www.depe
On 12/04/2011 08:54 PM, dmigow...@ikoffice.de wrote:
The following bug has been logged on the website:
Bug reference: 6325
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 8.3.16
Operating system: Linux
Description:
It seems that an update
The following bug has been logged on the website:
Bug reference: 6325
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 8.3.16
Operating system: Linux
Description:
It seems that an update to a row in a table always removes the element
