From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Luis Marin <luismarinaray@gmail.com>
To: pgsql-admin@postgresql.org
To: pgsql-general@postgresql.org
Subject: Re: Ideas to deal with table corruption
Date: Sat, 6 Jan 2018 09:39:59 -0800
Message-ID: <e16e848d-987e-7716-efc4-30e56369c1a0@aklaver.com> (raw)
In-Reply-To: <CAEp6HQXseuvaU_UGOju3rMduhHB+QTYcZa5oda+_82eQ73DVtw@mail.gmail.com>
References: <CAEp6HQXseuvaU_UGOju3rMduhHB+QTYcZa5oda+_82eQ73DVtw@mail.gmail.com>
On 01/06/2018 02:11 AM, Luis Marin wrote:
>
> Dear community,
>
> I am looking for ideas, to help me, check what is happening with a
> possible table corruption, I have some FK that works ok, but some stay
> in the state waiting forever, however selecting the same table works fine.
From further comments below I think you are talking about creating a FK
on a table, is that correct?
If not, what are you trying to do?
The table schema and code showing your process would be helpful.
And yes tailing the Postgres log file during the above could be helpful.
>
> Since, I am a newbie, in PostgreSQL, what should be my firsts steps, in
> order to have an idea how to fix this problem.
>
> I am thinking in watching my postgresql log error file during the
> requests for creating our FK,
> What do you suggest me
>
> Centos 7.2
> Postgresql 9.4
>
> Thanks
--
Adrian Klaver
adrian.klaver@aklaver.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: adrian.klaver@aklaver.com, luismarinaray@gmail.com, pgsql-general@postgresql.org
Subject: Re: Ideas to deal with table corruption
In-Reply-To: <e16e848d-987e-7716-efc4-30e56369c1a0@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox