Re: General: Unable to start the postgresql after copying postgresql.log

Поиск
Список
Период
Сортировка
От Pavan Teja
Тема Re: General: Unable to start the postgresql after copying postgresql.log
Дата
Msg-id CACh9nsac+07g6jvv4-24Kcv-XHHwqAFKW0eWkAA7seDcrSumRA@mail.gmail.com
обсуждение исходный текст
Ответ на General: Unable to start the postgresql after copying postgresql.log  (neela <neelat100@gmail.com>)
Ответы Re: General: Unable to start the postgresql after copyingpostgresql.log  (neela <neelat100@gmail.com>)
Список pgsql-bugs
Hi neela,

In this case, you can delete the postmaster.pid file and try to restart the Postgresql database.

I hope it might start. Kindly acknowledge for further queries if any.

Regards,
Pavan,
9841380956

On Wed, Oct 10, 2018, 7:26 PM neela <neelat100@gmail.com> wrote:


Dear sir/mam,
    I'm using postgresql 9.4.6 version.
    I've copied the postgresql.log as postgresql.log_bk.
    While copying the postgresql.log, I've restarted the postgresql process.
    Then the process got failed and I've got the following error,

        psql: could not connect to server: Connection refused
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

    And then I've check with log, it gives the result as follow,
    FATAL:  pre-existing shared memory block is still in use
    HINT:  If you're sure there are no old server processes still running,
    remove the shared memory block or just delete the file "postmaster.pid".

    After that unable to restart the postgresql, it always fails.
    After rebooting it gets succeed and truncating postmaster.pid gets succeed.
    Kindly help me how to fix this.

--    
with regards,
Neelaveni

В списке pgsql-bugs по дате отправления:

Предыдущее
От: neela
Дата:
Сообщение: General: Unable to start the postgresql after copying postgresql.log
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15425: DETACH/ATTACH PARTITION bug