Gordon Shannon <gordo169@xxxxxxxxx> writes: > Sorry, I left that out. Yeah, I wondered that too, since these tables do > not use toast. Hm. Well, given that the stack trace suggests we're trying to access a tuple value that's not there (bogus pointer, or data overwritten since the pointer was created), the "invalid memory alloc request size" message is believable as another manifestation of the same problem. The odds seem pretty good that the "corrupt compressed data" message has the same origin at bottom, although the lack of any obvious data to be compressed in this table is confusing. Maybe you could get that from trying to copy over a garbage value of that one varchar column, though. I tried to replicate the problem here without success, which suggests to me that maybe it's plan-dependent. Can you show what EXPLAIN gives you for the troublesome query? Another point here is that your logs suggest that the query blocked behind the previous updater of the row for a very long time --- 90 sec in one case, 30 sec in another. Is that the typical runtime for one of these updates? If not, can you identify what the blocking query was? If it's something different from another instance of the identical update, it'd be useful to know what. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
