On 3/13/19 1:59 PM, Mariel Cherkassky wrote:
Hey,
The query was the first thing that I tried, it didnt solve the issue.
Guess I'll update to the latest version.
I read releases notes and I don't find any item that could be related to
the error you encounter. It could be either another bug in p
Hey,
The query was the first thing that I tried, it didnt solve the issue.
Guess I'll update to the latest version.
בתאריך יום ד׳, 13 במרץ 2019 ב-14:48 מאת Alexandre Arruda <
adald...@gmail.com>:
> To avoid a dump/restore, use this:
>
> psql -o /dev/null -c "select * from table for update
To avoid a dump/restore, use this:
psql -o /dev/null -c "select * from table for update" database
Using the last releases of the major versions solve the bug for me.
Best regards
Em qua, 13 de mar de 2019 às 09:29, Mariel Cherkassky <
mariel.cherkas...@gmail.com> escreveu:
> Hey,
> The logs ar
Hey,
The logs are full of info that I cant share. However, it full of the next
messages :
ERROR: found xmin 16804535 from before relfrozenxid 90126924
CONTEXT: automatic vacuum of table db1.public.table_1"
...
What I'm trying to understand here is if the bug was fixed or not. In the
first time i
On 3/12/19 8:58 AM, Mariel Cherkassky wrote:
Apparently the issue appeared again in the same database but on
different table . In the last time dumping and restoring the table
helped. However, I dont understand why another table hit the bug if it
was fixed in 9.6.9 while my db version is 9.6.10
Hi All,
Apparently the issue appeared again in the same database but on different
table . In the last time dumping and restoring the table helped. However, I
dont understand why another table hit the bug if it was fixed in 9.6.9
while my db version is 9.6.10.
Any idea ?
בתאריך יום ב׳, 4 בפבר׳ 20
dumping the table and then restoring it solved the case for me. select for
update didnt help..
thanks !
בתאריך יום ד׳, 30 בינו׳ 2019 ב-12:35 מאת Mariel Cherkassky <
mariel.cherkas...@gmail.com>:
> Hey,
> As I said, I'm getting this error for all the objects in a specific db. I
> cant eve
Hey,
As I said, I'm getting this error for all the objects in a specific db. I
cant even connect to the database, I immediatly getting this error.
The bug was fixed in 9.6.10 but the db version is 9.6.10 so how can it
happen ? The db was installed in that version from the first place and *no
upgrad
On 2019-Jan-30, Mariel Cherkassky wrote:
> It seems that the version of the db is 9.6.10 :
>
> psql -U db -d db -c "select version()";
> Password for user db:
> version
> ---
> PostgreSQL 9.6.1
It seems that the version of the db is 9.6.10 :
psql -U db -d db -c "select version()";
Password for user db:
version
---
PostgreSQL 9.6.10 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7
20
On 1/26/19 11:56 AM, Mariel Cherkassky wrote:
Update to the minor version should be an easy solution - yum update
postgresql . What did you mean by carful
Sorry, I meant, do not forget to apply update to be sure same bug do not
happen again.
Update to the minor version should be an easy solution - yum update
postgresql . What did you mean by carful
On Sat, Jan 26, 2019, 12:48 PM Adrien NAYRAT On 1/25/19 6:20 PM, Mariel Cherkassky wrote:
> > I'm getting this issue when I try to connect to a specific db. Does it
> > matters what table
On 1/25/19 6:20 PM, Mariel Cherkassky wrote:
I'm getting this issue when I try to connect to a specific db. Does it
matters what table I specify ? Should I just choose a random table from
the problematic db? If I'll dump the db and restore it it can help ?
Error message is on "db1.public.table
I'm getting this issue when I try to connect to a specific db. Does it
matters what table I specify ? Should I just choose a random table from the
problematic db? If I'll dump the db and restore it it can help ?
On Fri, Jan 25, 2019, 10:19 AM Adrien NAYRAT On 1/24/19 3:14 PM, Mariel Cherkassky wr
On 1/24/19 3:14 PM, Mariel Cherkassky wrote:
I'm checking the full version.
As you said I saw that in 9.6.9 there was a fix for the next bug :
Avoid spuriously marking pages as all-visible (Dan Wood, Pavan Deolasee,
Álvaro Herrera)
This could happen if some tuples were locked (but not deleted
I'm checking the full version.
As you said I saw that in 9.6.9 there was a fix for the next bug :
Avoid spuriously marking pages as all-visible (Dan Wood, Pavan Deolasee,
Álvaro Herrera)
This could happen if some tuples were locked (but not deleted). While
queries would still function correctly,
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
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
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
19 matches
Mail list logo
