On Thu, Nov 07, 2019 at 12:55:13PM +0900, Michael Paquier wrote:
> So, are there plans to move on with this patch? It is waiting on
> author for some time now.
Seeing no activity from the author or even the reviewer, I have marked
the patch as returned with feedback for now. I am not actually
On Thu, Sep 05, 2019 at 07:09:45PM -0400, Alvaro Herrera from 2ndQuadrant wrote:
> Can't we have pg_ctl just continue to wait indefinitely? So we'd set
> SERVICE_START_PENDING when wait_for_postmaster is out of patience, then
> loop again -- until recovery completes. Exiting pg_ctl on timeout
On 2019-Jul-24, Kyotaro Horiguchi wrote:
> > Please find the proposed patch for review. I will attach it to
> > commitfest as well
>
> Pacemaker suffers the same thing. We suggest our customers that "start
> server alone to perform recovery then start pacemaker if it is
> expected to take a long
Sorry in advance for link-breaking message, but the original mail was
too old and gmail doesn't allow me to craft required headers to link
to it.
https://www.postgresql.org/message-id/CAKm4Xs71Ma8bV1fY6Gfz9Mg3AKmiHuoJNpxeDVF_KTVOKoy1WQ%40mail.gmail.com
> Please find the proposed patch for
Hi,
+ case POSTMASTER_STILL_STARTING:
+ write_eventlog(EVENTLOG_ERROR_TYPE, _("Timed out waiting for
server startup\n"));
+ pgwin32_SetServiceStatus(SERVICE_START_PENDING);
+ return;
Could this patch solve first post's problem [1] ?
I think
Hi,
Please find the proposed patch for review. I will attach it to commitfest
as well
Regards,
Ram.
windows_service_bug_fix_v2.patch
Description: Binary data
Hi,
Thank you for picking up this and I'm sorry for delay reply.
>> If wait_for_postmaster returns POSTMASTER_STILL_STARTING will it
>> be correct to set the status of windows service to SERVICE_START_PENDING ?
Yes, I think this is the best. Currently, I do not have good solution to change
Hi,
If wait_for_postmaster returns POSTMASTER_STILL_STARTING will it be correct
to set the status of windows service to SERVICE_START_PENDING ?
I would like to take this up if no one is working on this.
Regards,
Ram.
Hi Higuchi-san,
(1)
What made you think this problem rarely occurs in PG 10 or later? Looking at
the following code, this seems to happen in PG 10+ too.
if (do_wait)
{
write_eventlog(EVENTLOG_INFORMATION_TYPE, _("Waiting for server
startup...\n"));
if
Michael Paquier wrote:
> You should register this patch to the next commit fest in the section for bug
> fixes to not lose sight of it;
Thank you for picking up my post. I registered to the next CF.
> I haven't put much thoughts into what you propose here, but this status
> message is not
On Wed, Jan 09, 2019 at 05:28:29AM +, Higuchi, Daisuke wrote:
> One solution is that status of Windows Service should be changed to
> "SERVICE_RUNNING" even if timeout is occurred because of long time
> recovery. I attached the patch of this solution.
You should register this patch to the
Hi,
This thread is inactive, but I want to solve this problem.
I think this problem rarely occurs in 10 or later version because of commit
[1]. Because "pg_ctl start -w" wait for only PID file creation. It means that
timeout is not occurred even if crash recovery takes a lot of times.
Sakai, Teppei wrote:
> This is my first posting to the mailing list.
>
> Currently our customer uses PostgreSQL 9.5 and hits problem during Windows
> service start.
> The Windows service status of the instance is different from actual status.
>
> We got the following situation.
> 1. Register
13 matches
Mail list logo