[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] Fixup Server failed
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-bugs] Fixup Server failed |
Date: |
Mon, 2 Sep 2019 22:55:10 +0200 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Mon, Sep 02, 2019 at 10:30:59PM +0200, slappinjohn wrote:
> pk_audit | row_version | modified_when | modified_by |
> pk | user_action
> ----------+-------------+-------------------------------+-------------+-------+-----------------------------------------------
> 593079 | 0 | 2019-07-23 06:26:59.141724+00 | maan |
> 67314 | EMR access: pulling chart for identity [9672]
> (1 Zeile)
I had outsmarted myself: the old index still exists, and
points to one of the rows (this one) with the pk of 67314.
However, we need both, so we need to switch off the index for
that query.
set enable_indexonlyscan to off;
set enable_indexscan to off;
SELECT * FROM gm.access_log WHERE pk = 67314;
This should return both rows.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
- [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/02
- Re: [Gnumed-bugs] Fixup Server failed, Karsten Hilbert, 2019/09/02
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/02
- Re: [Gnumed-bugs] Fixup Server failed,
Karsten Hilbert <=
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/03
- Re: [Gnumed-bugs] Fixup Server failed, Karsten Hilbert, 2019/09/03
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/03
- Re: [Gnumed-bugs] Fixup Server failed, Karsten Hilbert, 2019/09/03
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/04
- Message not available
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/04
- Re: [Gnumed-bugs] Fixup Server failed, Karsten Hilbert, 2019/09/04
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/05
- Re: [Gnumed-bugs] Fixup Server failed, Karsten Hilbert, 2019/09/05
- Re: [Gnumed-bugs] Fixup Server failed, slappinjohn, 2019/09/05