Yeah 9.6 !
On Wed, Jan 23, 2019, 9:51 PM Jerry Sievers Mariel Cherkassky writes:
>
> > Hey,
> > I'm trying to help a guy that is using pg9.6 but I'm not so familiar
> > with the error message :
> > ERROR: found xmin 16804535 from before relfrozenxid 90126924
> > CONTEXT: automatic vacuum of ta
On Wed, 2019-01-23 at 10:28 -0700, Jan Nielsen wrote:
> select
> order0_.id as id1_7_,
> order0_.created_by as created_2_7_,
> order0_.created_date as created_3_7_,
> order0_.last_modified_by as last_mod4_7_,
> order0_.last_modified_date as last_mod5_7_,
Mariel Cherkassky writes:
> Hey,
> I'm trying to help a guy that is using pg9.6 but I'm not so familiar
> with the error message :
> ERROR: found xmin 16804535 from before relfrozenxid 90126924
> CONTEXT: automatic vacuum of table db1.public.table_1"
9.6.?...
That error or a very similar one
Hi,
is there an index on
fm_order(session_id,type)
?
regards
PAscal
Hi,
Please pardon me if this question is already answered in the documentation,
Wiki, or the mailing list archive. The problem is, that I don't know the
exact term to search for - I've tried searching for "linear scalability"
and "concurrency vs performance" but didn't find what I was looking for.
On Wed, Jan 23, 2019 at 6:51 AM Jim Finnerty wrote:
> One thing that isn't helping is that you have a redundant predicate. The
> selectivity of this predicate is also estimated too low, so removing the
> redundant predicate might improve the estimate and change the plan:
>
> (
Hey,
I'm trying to help a guy that is using pg9.6 but I'm not so familiar with
the error message :
ERROR: found xmin 16804535 from before relfrozenxid 90126924
CONTEXT: automatic vacuum of table db1.public.table_1"
It seems that the error has started appearing two weeks ago. Data that I
collec
