| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Kevin McKibbin <kevinmckibbin123(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgbench: could not connect to server: Resource temporarily unavailable |
| Date: | 2022-08-24 02:55:31 |
| Message-ID: | CA+hUKGL7MaCa=8syBxasMdOkkv1=hw3KhU1oEVekqFGNfgpv0g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 23, 2022 at 2:42 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> > 0002 isn't quite related, but while writing 0001 I noticed a nearby
> > use of /proc/sys/... which I thought should be converted to sysctl.
> > IMO /proc/sys pretty much sucks, at least for documentation purposes,
> > for multiple reasons:
Oh, one comment there is actually obsolete now AFAIK. Unless there is
some reason to think personality(ADDR_NO_RANDOMIZE) might not work in
some case where sysctl -w kernel.randomize_va_space=0 will, I think we
can just remove that.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Remove-obsolete-comment.patch | text/x-patch | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-08-24 03:06:33 | Re: pgbench: could not connect to server: Resource temporarily unavailable |
| Previous Message | Thomas Munro | 2022-08-23 03:58:26 | Re: pgbench: could not connect to server: Resource temporarily unavailable |