On Tue, Oct 31, 2023 at 11:24:24AM -0400, Bruce Momjian wrote:
> On Tue, Oct 31, 2023 at 11:16:29AM -0400, Bruce Momjian wrote:
> > On Wed, Jul 27, 2022 at 09:28:51PM -0700, David G. Johnston wrote:
> > > On Wed, Jul 27, 2022 at 8:22 PM Tom Lane wrote:
> > >
> > > I wrote:
> > > > If EDB
On Tue, Oct 31, 2023 at 11:16:29AM -0400, Bruce Momjian wrote:
> On Wed, Jul 27, 2022 at 09:28:51PM -0700, David G. Johnston wrote:
> > On Wed, Jul 27, 2022 at 8:22 PM Tom Lane wrote:
> >
> > I wrote:
> > > If EDB isn't adequately filling in the documentation for the behavior
> > >
On Wed, Jul 27, 2022 at 09:28:51PM -0700, David G. Johnston wrote:
> On Wed, Jul 27, 2022 at 8:22 PM Tom Lane wrote:
>
> I wrote:
> > If EDB isn't adequately filling in the documentation for the behavior
> > of their packaging, that's on them.
>
> Having now looked more closely
On Wed, Jul 27, 2022 at 8:22 PM Tom Lane wrote:
> I wrote:
> > If EDB isn't adequately filling in the documentation for the behavior
> > of their packaging, that's on them.
>
> Having now looked more closely at the pg_upgrade documentation,
> I don't think this is exactly EDB's fault; it's text
I wrote:
> If EDB isn't adequately filling in the documentation for the behavior
> of their packaging, that's on them.
Having now looked more closely at the pg_upgrade documentation,
I don't think this is exactly EDB's fault; it's text that should
never have been there to begin with. ISTM we
On Wed, Jul 27, 2022 at 07:31:35PM -0700, David G. Johnston wrote:
>
> Ultimately we do our users the best service if when they operate an
> installation using defaults that they have documentation showing how to
> perform something like an upgrade that works with those defaults.
I don't really
"David G. Johnston" writes:
> On Wed, Jul 27, 2022 at 6:42 PM Julien Rouhaud wrote:
>> Note that there's no "official" Windows installer,
Yeah, that.
> Our technical definition aside, the fact is our users consider the sole EDB
> installer to be official.
> If the ultimate solution is to
On Wednesday, July 27, 2022, Julien Rouhaud wrote:
> On Wed, Jul 27, 2022 at 07:02:51PM -0700, David G. Johnston wrote:
> >
> > In the end the problem is ours and cannot be simply assigned to a
> > third-party. So let's resolve it here (on this list, whatever the
> > solution) where
On Wed, Jul 27, 2022 at 07:02:51PM -0700, David G. Johnston wrote:
>
> In the end the problem is ours and cannot be simply assigned to a
> third-party. So let's resolve it here (on this list, whatever the
> solution) where representatives from all parties are present.
We could amend the
On Wed, Jul 27, 2022 at 6:42 PM Julien Rouhaud wrote:
> Hi,
>
> On Wed, Jul 27, 2022 at 11:36:11PM +0200, Thomas Kellerer wrote:
> > David G. Johnston schrieb am 27.07.2022 um 21:21:
> > > And then there is the issue of file ownership.
> > >
> > > Assuming we want better documentation for this
Hi,
On Wed, Jul 27, 2022 at 11:36:11PM +0200, Thomas Kellerer wrote:
> David G. Johnston schrieb am 27.07.2022 um 21:21:
> > And then there is the issue of file ownership.
> >
> > Assuming we want better documentation for this specific issue for
> > back-patching what would that look like?
> >
David G. Johnston schrieb am 27.07.2022 um 21:21:
And then there is the issue of file ownership.
Assuming we want better documentation for this specific issue for
back-patching what would that look like?
Going forward should our installer be creating the postgres user for
consistency with
Hey,
Just interacted with a frustrated user on Slack trying to upgrade from v13
to v14 on Windows. Our official download page for the Windows installer
claims the core documentation as its official reference - can someone
responsible for this area please suggest and test some changes to make
13 matches
Mail list logo