public inbox for [email protected]
help / color / mirror / Atom feedDocumentation Suggestion
13+ messages / 6 participants
[nested] [flat]
* Documentation Suggestion
@ 2022-04-28 19:11 PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: PG Doc comments form @ 2022-04-28 19:11 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/app-initdb.html
Description:
Reference: https://www.postgresql.org/docs/11/app-initdb.html
When installing recently I found the "-A " option of the initdb command only
accepts lowercase argument. For example "-A LDAP" is not valid and must be
"-A ldap" otherwise the following error is returned:
initdb: invalid authentication method "LDAP" for "local" connections
It may be worth adding a note to the above documentation that states all
option values must be specified in lowercase.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
@ 2022-04-28 20:15 ` David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: David G. Johnston @ 2022-04-28 20:15 UTC (permalink / raw)
To: [email protected]; Pg Docs <[email protected]>
On Thu, Apr 28, 2022 at 12:36 PM PG Doc comments form <
[email protected]> wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/app-initdb.html
> Description:
>
> Reference: https://www.postgresql.org/docs/11/app-initdb.html
>
> When installing recently I found the "-A " option of the initdb command
> only
> accepts lowercase argument. For example "-A LDAP" is not valid and must be
> "-A ldap" otherwise the following error is returned:
> initdb: invalid authentication method "LDAP" for "local" connections
>
> It may be worth adding a note to the above documentation that states all
> option values must be specified in lowercase.
>
The -A option will accept any of the option names that are specified in the
documentation for pg_hba.conf
It just so happens that all of those names, at present, consist of all
lower-case characters.
That matching is case-sensitive is not specifically stated but is the
default unless otherwise stated.
The page could use a hyperlink/cross-reference to the pg_hba.conf
documentation.
But we don't go out of our way anywhere else to be so explicit about this
kind of requirement and don't see a point of making this instance an
exception.
David J.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
@ 2022-04-29 09:09 ` Alvaro Herrera <[email protected]>
2022-04-29 09:52 ` Re: Documentation Suggestion Peter Eisentraut <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
0 siblings, 2 replies; 13+ messages in thread
From: Alvaro Herrera @ 2022-04-29 09:09 UTC (permalink / raw)
To: David G. Johnston <[email protected]>; +Cc: [email protected]; Pg Docs <[email protected]>
On 2022-Apr-28, David G. Johnston wrote:
> But we don't go out of our way anywhere else to be so explicit about this
> kind of requirement and don't see a point of making this instance an
> exception.
Maybe we could add a <para> in the Options section before the item list,
along the lines of "be mindful that arguments to options --auth,
--auth-local, --encoding, --locale (and all --lc-* options) are
case-sensitive".
(The point here, I suppose, is that LDAP being an acronym is typically
spelled uppercase, so our use of lowercase is a bit odd.)
Maybe there are other places where this is relevant as well?
> The page could use a hyperlink/cross-reference to the pg_hba.conf
> documentation.
That's easily fixed. How about the attached patch?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El destino baraja y nosotros jugamos" (A. Schopenhauer)
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
@ 2022-04-29 09:52 ` Peter Eisentraut <[email protected]>
1 sibling, 0 replies; 13+ messages in thread
From: Peter Eisentraut @ 2022-04-29 09:52 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; David G. Johnston <[email protected]>; +Cc: [email protected]; Pg Docs <[email protected]>
On 29.04.22 11:09, Alvaro Herrera wrote:
> + <para>
> + Be mindful that arguments to options <option>--auth</option>,
> + <option>--auth-local</option>, <option>--encoding</option>,
> + <option>--locale</option> (and all <option>--lc-*</option> options) are
> + case-sensitive.
> + </para>
Almost all arguments of command-line options of all PostgreSQL tools are
case-sensitive. Consider the initdb -U option for example. By pointing
out a couple of specific cases, wouldn't we also create more confusion
about options not mentioned?
(I'm not sure about the case-sensitivity of the locale options. That
could be OS-dependent.)
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
@ 2022-04-29 14:06 ` Tom Lane <[email protected]>
2022-04-29 15:05 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
1 sibling, 2 replies; 13+ messages in thread
From: Tom Lane @ 2022-04-29 14:06 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
Alvaro Herrera <[email protected]> writes:
> On 2022-Apr-28, David G. Johnston wrote:
>> But we don't go out of our way anywhere else to be so explicit about this
>> kind of requirement and don't see a point of making this instance an
>> exception.
> Maybe we could add a <para> in the Options section before the item list,
> along the lines of "be mindful that arguments to options --auth,
> --auth-local, --encoding, --locale (and all --lc-* options) are
> case-sensitive".
I don't think this is an improvement, mainly for the reason David
mentions: why wouldn't you need a similar statement on every single
one of our program man pages?
>> The page could use a hyperlink/cross-reference to the pg_hba.conf
>> documentation.
> That's easily fixed. How about the attached patch?
That part's OK, but personally I'd only have cited the link once.
regards, tom lane
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
@ 2022-04-29 15:05 ` David G. Johnston <[email protected]>
1 sibling, 0 replies; 13+ messages in thread
From: David G. Johnston @ 2022-04-29 15:05 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; [email protected]; Pg Docs <[email protected]>
On Fri, Apr 29, 2022 at 7:07 AM Tom Lane <[email protected]> wrote:
> Alvaro Herrera <[email protected]> writes:
> > On 2022-Apr-28, David G. Johnston wrote:
>
> >> The page could use a hyperlink/cross-reference to the pg_hba.conf
> >> documentation.
>
> > That's easily fixed. How about the attached patch?
>
> That part's OK, but personally I'd only have cited the link once.
>
>
Agreed, one or three, including the local-only option but ignoring the
host-only one seems like a mistake.
I would just document the -A/--auth-method option, the other two are close
enough in space to borrow it just fine.
Shall we do a return link from the pg_hba.conf to initdb? The first
paragraph already has:
"A default pg_hba.conf file is installed when the data directory is
initialized by initdb."
David J.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
@ 2022-05-13 18:41 ` Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
1 sibling, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2022-05-13 18:41 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
On Fri, Apr 29, 2022 at 10:06:57AM -0400, Tom Lane wrote:
> Alvaro Herrera <[email protected]> writes:
> > On 2022-Apr-28, David G. Johnston wrote:
> >> But we don't go out of our way anywhere else to be so explicit about this
> >> kind of requirement and don't see a point of making this instance an
> >> exception.
>
> > Maybe we could add a <para> in the Options section before the item list,
> > along the lines of "be mindful that arguments to options --auth,
> > --auth-local, --encoding, --locale (and all --lc-* options) are
> > case-sensitive".
>
> I don't think this is an improvement, mainly for the reason David
> mentions: why wouldn't you need a similar statement on every single
> one of our program man pages?
I think the confusion is that while the option arguments are
case-sensitive, many of the values are typically used as all upper-case,
and I think any doc mention would have to include that:
Note that valid --auth option values are all lower case, even
for authentication types that typically appear as all upper case,
e.g., "LDAP".
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
@ 2022-05-14 15:21 ` Alvaro Herrera <[email protected]>
2022-05-24 12:36 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Alvaro Herrera @ 2022-05-14 15:21 UTC (permalink / raw)
To: Bruce Momjian <[email protected]>; +Cc: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
I pushed the other suggested bits.
On 2022-May-13, Bruce Momjian wrote:
> On Fri, Apr 29, 2022 at 10:06:57AM -0400, Tom Lane wrote:
> > I don't think this is an improvement, mainly for the reason David
> > mentions: why wouldn't you need a similar statement on every single
> > one of our program man pages?
>
> I think the confusion is that while the option arguments are
> case-sensitive, many of the values are typically used as all upper-case,
> and I think any doc mention would have to include that:
>
> Note that valid --auth option values are all lower case, even
> for authentication types that typically appear as all upper case,
> e.g., "LDAP".
Yeah, that was my initial thought too. The case-sensitivity is a
consideration for other things too (such as locale or encoding names),
but for those we do match the operating system name exactly, rather than
using our own lower-case version of it, which nobody else uses.
So really the point is not about the fact that it is case sensitive as
that the case of our name doesn't match the usual one. Maybe the note
should be "Note that authentication types are all lower case, [even for
...]" or something like that.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"I can see support will not be a problem. 10 out of 10." (Simon Wittber)
(http://archives.postgresql.org/pgsql-general/2004-12/msg00159.php)
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
@ 2022-05-24 12:36 ` Bruce Momjian <[email protected]>
2022-07-14 22:23 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2022-05-24 12:36 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
fOn Sat, May 14, 2022 at 05:21:58PM +0200, Álvaro Herrera wrote:
> I pushed the other suggested bits.
>
> On 2022-May-13, Bruce Momjian wrote:
>
> > On Fri, Apr 29, 2022 at 10:06:57AM -0400, Tom Lane wrote:
>
> > > I don't think this is an improvement, mainly for the reason David
> > > mentions: why wouldn't you need a similar statement on every single
> > > one of our program man pages?
> >
> > I think the confusion is that while the option arguments are
> > case-sensitive, many of the values are typically used as all upper-case,
> > and I think any doc mention would have to include that:
> >
> > Note that valid --auth option values are all lower case, even
> > for authentication types that typically appear as all upper case,
> > e.g., "LDAP".
>
> Yeah, that was my initial thought too. The case-sensitivity is a
> consideration for other things too (such as locale or encoding names),
> but for those we do match the operating system name exactly, rather than
> using our own lower-case version of it, which nobody else uses.
>
> So really the point is not about the fact that it is case sensitive as
> that the case of our name doesn't match the usual one. Maybe the note
> should be "Note that authentication types are all lower case, [even for
> ...]" or something like that.
Agreed.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-05-24 12:36 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
@ 2022-07-14 22:23 ` Bruce Momjian <[email protected]>
2022-07-21 17:58 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2022-07-14 22:23 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
On Tue, May 24, 2022 at 08:36:18AM -0400, Bruce Momjian wrote:
> fOn Sat, May 14, 2022 at 05:21:58PM +0200, Álvaro Herrera wrote:
> > On 2022-May-13, Bruce Momjian wrote:
> > > Note that valid --auth option values are all lower case, even
> > > for authentication types that typically appear as all upper case,
> > > e.g., "LDAP".
> >
> > Yeah, that was my initial thought too. The case-sensitivity is a
> > consideration for other things too (such as locale or encoding names),
> > but for those we do match the operating system name exactly, rather than
> > using our own lower-case version of it, which nobody else uses.
> >
> > So really the point is not about the fact that it is case sensitive as
> > that the case of our name doesn't match the usual one. Maybe the note
> > should be "Note that authentication types are all lower case, [even for
> > ...]" or something like that.
Here is a patch that implements this.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
Attachments:
[text/x-diff] auth.diff (746B, 2-auth.diff)
download | inline diff:
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index b2a459fb0d..433759928b 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -417,7 +417,9 @@ hostnogssenc <replaceable>database</replaceable> <replaceable>user</replaceabl
<para>
Specifies the authentication method to use when a connection matches
this record. The possible choices are summarized here; details
- are in <xref linkend="auth-methods"/>.
+ are in <xref linkend="auth-methods"/>. All the options
+ are lower case and treated case sensitively, so even acronyms like
+ <literal>ldap</literal> must be specified as lower case.
<variablelist>
<varlistentry>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-05-24 12:36 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-07-14 22:23 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
@ 2022-07-21 17:58 ` Bruce Momjian <[email protected]>
2022-07-21 18:05 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2022-07-21 17:58 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
On Thu, Jul 14, 2022 at 06:23:43PM -0400, Bruce Momjian wrote:
> On Tue, May 24, 2022 at 08:36:18AM -0400, Bruce Momjian wrote:
> > fOn Sat, May 14, 2022 at 05:21:58PM +0200, Álvaro Herrera wrote:
> > > On 2022-May-13, Bruce Momjian wrote:
> > > > Note that valid --auth option values are all lower case, even
> > > > for authentication types that typically appear as all upper case,
> > > > e.g., "LDAP".
> > >
> > > Yeah, that was my initial thought too. The case-sensitivity is a
> > > consideration for other things too (such as locale or encoding names),
> > > but for those we do match the operating system name exactly, rather than
> > > using our own lower-case version of it, which nobody else uses.
> > >
> > > So really the point is not about the fact that it is case sensitive as
> > > that the case of our name doesn't match the usual one. Maybe the note
> > > should be "Note that authentication types are all lower case, [even for
> > > ...]" or something like that.
>
> Here is a patch that implements this.
Patch applied to all supported branches.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-05-24 12:36 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-07-14 22:23 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-07-21 17:58 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
@ 2022-07-21 18:05 ` Alvaro Herrera <[email protected]>
2022-07-21 18:43 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
0 siblings, 1 reply; 13+ messages in thread
From: Alvaro Herrera @ 2022-07-21 18:05 UTC (permalink / raw)
To: Bruce Momjian <[email protected]>; +Cc: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
On 2022-Jul-21, Bruce Momjian wrote:
> Patch applied to all supported branches.
Thanks, looks good.
I notice you credited me as the reporter, but actually the reporter is
[email protected].
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Documentation Suggestion
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` Re: Documentation Suggestion David G. Johnston <[email protected]>
2022-04-29 09:09 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-04-29 14:06 ` Re: Documentation Suggestion Tom Lane <[email protected]>
2022-05-13 18:41 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
2022-05-24 12:36 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-07-14 22:23 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-07-21 17:58 ` Re: Documentation Suggestion Bruce Momjian <[email protected]>
2022-07-21 18:05 ` Re: Documentation Suggestion Alvaro Herrera <[email protected]>
@ 2022-07-21 18:43 ` Bruce Momjian <[email protected]>
0 siblings, 0 replies; 13+ messages in thread
From: Bruce Momjian @ 2022-07-21 18:43 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: Tom Lane <[email protected]>; David G. Johnston <[email protected]>; [email protected]; Pg Docs <[email protected]>
On Thu, Jul 21, 2022 at 08:05:49PM +0200, Álvaro Herrera wrote:
> On 2022-Jul-21, Bruce Momjian wrote:
>
> > Patch applied to all supported branches.
>
> Thanks, looks good.
>
> I notice you credited me as the reporter, but actually the reporter is
> [email protected].
Oh, my apologies. I had not kept the first email and didn't notice the
"Re:".
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2022-07-21 18:43 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-04-28 19:11 Documentation Suggestion PG Doc comments form <[email protected]>
2022-04-28 20:15 ` David G. Johnston <[email protected]>
2022-04-29 09:09 ` Alvaro Herrera <[email protected]>
2022-04-29 09:52 ` Peter Eisentraut <[email protected]>
2022-04-29 14:06 ` Tom Lane <[email protected]>
2022-04-29 15:05 ` David G. Johnston <[email protected]>
2022-05-13 18:41 ` Bruce Momjian <[email protected]>
2022-05-14 15:21 ` Alvaro Herrera <[email protected]>
2022-05-24 12:36 ` Bruce Momjian <[email protected]>
2022-07-14 22:23 ` Bruce Momjian <[email protected]>
2022-07-21 17:58 ` Bruce Momjian <[email protected]>
2022-07-21 18:05 ` Alvaro Herrera <[email protected]>
2022-07-21 18:43 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox