| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [bug fix] "pg_ctl stop" times out when it should respond quickly |
| Date: | 2014-01-05 06:49:14 |
| Message-ID: | 391DE5AF03594C9A9DD425F578B94268@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
> On 12/25/13, 6:40 AM, MauMau wrote:
>> pg_regress must wait for postgres to terminate by calling waitpid(),
>> because it invoked postgres directly. The attached
>> pg_regress_pg_stop.patch does this. If you like the combination of this
>> and the original fix for pg_ctl in one patch, please use
>> pg_stop_fail_v3.patch.
>
> This patch doesn't apply.
Is that true? Today, I downloaded the following file (whose timestamp was
2014-Jan-04), and could apply pg_stop_fail_v3.patch cleanly. The "make
check" succeeded.
http://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.gz
Could you confirm again and tell me what problem is happening?
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2014-01-05 07:40:17 | Re: [bug fix] multibyte messages are displayed incorrectly on the client |
| Previous Message | MauMau | 2014-01-05 06:42:42 | Re: [bug fix] ECPG app crashes due to SIGBUS on SPARC Solaris |