On Feb 26, 2014, at 2:59 AM, Tomas Vondra wrote:
> On 26 Únor 2014, 8:45, john gale wrote:
>
>> munin2=# delete from testruns where ctid = '(37069305,4)';
>> ERROR: tuple concurrently updated
>
> AFAIK this error is raised when a before trigger modifies the row that is
> being deleted. Imagin
On 26 Únor 2014, 8:45, john gale wrote:
>
> Does anybody have any ideas about this.
>
> We restarted the postmaster and the issue persists. So previously in
> 9.0.4 where we could clean corruption, it seems in 9.3.2 we can no longer
> clean corruption.o I'm assuming this because our data insert e
Does anybody have any ideas about this.
We restarted the postmaster and the issue persists. So previously in 9.0.4
where we could clean corruption, it seems in 9.3.2 we can no longer clean
corruption.o I'm assuming this because our data insert environment has not
changed, so we shouldn't be
We ran into an open file limit on the DB host (Mac OS X 10.9.0, Postgres 9.3.2)
and caused the familiar "ERROR: unexpected chunk number 0 (expected 1) for
toast value 155900302 in pg_toast_16822" when selecting data.
Previously when we've run into this kind of corruption we could find the
spe
