Re: VACUUM unable to accomplish because of a non-existent MultiXactId

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alvaro Herrera <alvherre@xxxxxxxxxxxxxxx> writes:
> Tom Lane wrote:
>> Couldn't creation and deletion of a toasted object within the same
>> transaction do it?

> I tried and couldn't find a way to cause one to appear.  When a row is
> created, it has xmax=0 so when it's deleted the xmax can just be set to
> the deleting xact.  And we don't ever update pg_toast rows, AFAIK.

Ah, nevermind, brain fade ... I was momentarily confusing this with
combo CIDs.  Right, there are no updates or row locks taken on toast
table rows (unless someone were to do one manually?)

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux