On Fri, Mar 8, 2013 at 10:26:21AM -0500, Robert Haas wrote:
> overhead seems badly overpriced for insert-only tables. These are not
> fundamental truths of the universe, or even of PostgreSQL; they are
> specific consequences of the representation we've chosen for heaps.
> Many of them are things
On Fri, Mar 8, 2013 at 8:58 AM, Andres Freund wrote:
> I'd be interested in something slightly related that is doing HOT on a
> per-index basis. Currently we don't do hot if any index is updated even
> though quite possibly most of the indexes don't change.
> I think that might result in some quit
On 2013-03-06 09:11:38 +0530, abhinav batra wrote:
> Hey
> I want to work towards the follwing feature in TODO list:
> Prevent index uniqueness checks when UPDATE does not modify the
> columnUniqueness
> (index) checks are done when updating a column even if the column is not
> modified by the UPDA
On Tue, Mar 5, 2013 at 10:41 PM, abhinav batra wrote:
> Hey
> I want to work towards the follwing feature in TODO list:
> Prevent index uniqueness checks when UPDATE does not modify the
> columnUniqueness (index) checks are done when updating a column even if the
> column is not modified by the UP
Hey
I want to work towards the follwing feature in TODO list:
Prevent index uniqueness checks when UPDATE does not modify the
columnUniqueness
(index) checks are done when updating a column even if the column is not
modified by the UPDATE. However, HOT already short-circuits this in common
cases, s
