Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq
Date
Msg-id CABUevEy1pfmX7ctHOX5qP+AyOuN_75zYa9iff2AG1OMBuOdGSQ@mail.gmail.com
Whole thread Raw
In response to [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq  (Phil Sorber <phil@omniti.com>)
Responses Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq
List pgsql-hackers
<p dir="ltr"><br /> On Feb 3, 2013 4:16 AM, "Phil Sorber" <<a href="mailto:phil@omniti.com">phil@omniti.com</a>>
wrote:<br/> ><br /> > This patch came up from discussion about pg_isready.<br /> ><br /> >
PQconninfoParseParamsis similar to PQconninfoParse but takes two<br /> > arrays like PQconnectdbParams. It
essentiallyexposes<br /> > conninfo_array_parse().<br /> ><br /> > PQconninfodefaultsMerge essentially exposes
conninfo_add_defaults().<br/> > It allows you to pass a PQconninfoOption struct and it adds defaults<br /> > for
allNULL values.<br /> ><br /> > There are no docs yet. I assumed I would let bikeshedding ensue, and<br /> >
alsodebate on whether we even want these first.<p dir="ltr">I think you forgot to attach the patch.<p dir="ltr">/Magnus

pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Setting visibility map in VACUUM's second phase
Next
From: Amit kapila
Date:
Subject: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block