From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL URI |
Date: | 2021-02-26 19:03:28 |
Message-ID: | 2F9DD553-0163-4576-A8D0-3F8CE13CABE4@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tom,
> On 26. Feb, 2021, at 19:02, Paul Förster <paul(dot)foerster(at)gmail(dot)com> wrote:
>
> as I said, I don't know how to write a patch. But I played around with diff & patch.
>
> However, does this do when applied to https://www.postgresql.org/docs/current/libpq-connect.html? Would this be what is needed?
sorry, I just realized I used a redundant @ character. So here's the corrected version.
Attachment | Content-Type | Size |
---|---|---|
libpq-connect.patch | application/octet-stream | 957 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-02-26 19:06:00 | Re: PostgreSQL Licensing Question for pg_crypto and tablefunc extensions |
Previous Message | Adrian Klaver | 2021-02-26 19:00:50 | Re: PostgreSQL Licensing Question for pg_crypto and tablefunc extensions |