On Sun, Feb 6, 2022 at 12:58 AM Noah Misch wrote:
>
> On Sun, Feb 06, 2022 at 12:41:52AM +0100, Magnus Hagander wrote:
> > On Sun, Feb 6, 2022 at 12:02 AM Noah Misch wrote:
> > > On Fri, Feb 04, 2022 at 01:36:46PM -0500, Bruce Momjian wrote:
> > > > On Wed, Feb 2, 2022 at 07:21:19PM -0700,
On Sun, Feb 6, 2022 at 5:28 AM Noah Misch wrote:
>
> > > - Canned responses are noise to every list reader other than the OP.
> > > - Canned responses make the list feel like a sales funnel rather than a
> > > normal
> > > free software mailing list.
> >
> > All bug reports posted through the
On Sun, Feb 06, 2022 at 12:41:52AM +0100, Magnus Hagander wrote:
> On Sun, Feb 6, 2022 at 12:02 AM Noah Misch wrote:
> > On Fri, Feb 04, 2022 at 01:36:46PM -0500, Bruce Momjian wrote:
> > > On Wed, Feb 2, 2022 at 07:21:19PM -0700, David G. Johnston wrote:
> > > > Have pg_lister queue up a check
On Sun, Feb 6, 2022 at 12:02 AM Noah Misch wrote:
>
> On Fri, Feb 04, 2022 at 01:36:46PM -0500, Bruce Momjian wrote:
> > On Wed, Feb 2, 2022 at 07:21:19PM -0700, David G. Johnston wrote:
> > > On Wed, Feb 2, 2022 at 5:35 PM Bruce Momjian wrote:
> > > Have pg_lister queue up a check for, say,
Hi,
On 2022-02-02 19:35:36 -0500, Bruce Momjian wrote:
> The Postgres community is great at diagnosing problems and giving users
> feedback. In most cases, we can either diagnose a problem and give a
> fix, or at least give users a hint at finding the cause.
>
> However, there is a class of
On Fri, Feb 04, 2022 at 01:36:46PM -0500, Bruce Momjian wrote:
> On Wed, Feb 2, 2022 at 07:21:19PM -0700, David G. Johnston wrote:
> > On Wed, Feb 2, 2022 at 5:35 PM Bruce Momjian wrote:
> > Have pg_lister queue up a check for, say, two or three days after the bug
> > reporting form is filled
On Fri, Feb 04, 2022 at 01:38:14PM -0500, Bruce Momjian wrote:
> On Thu, Feb 3, 2022 at 12:28:05PM +0800, Julien Rouhaud wrote:
>
> > One thing that might help would be to work on a troubleshooting section on
> > the
> > wiki with some common problems and some clear instructions on either how
On Thu, Feb 3, 2022 at 12:28:05PM +0800, Julien Rouhaud wrote:
> Hi,
>
> On Wed, Feb 02, 2022 at 07:35:36PM -0500, Bruce Momjian wrote:
> > The Postgres community is great at diagnosing problems and giving users
> > feedback. In most cases, we can either diagnose a problem and give a
> > fix,
On Wed, Feb 2, 2022 at 07:21:19PM -0700, David G. Johnston wrote:
> On Wed, Feb 2, 2022 at 5:35 PM Bruce Momjian wrote:
>
> I consider these as problems that need digging to find the cause, and
> users are usually unable to do sufficient digging, and we don't have
> time to give
Hi,
On Wed, Feb 02, 2022 at 07:35:36PM -0500, Bruce Momjian wrote:
> The Postgres community is great at diagnosing problems and giving users
> feedback. In most cases, we can either diagnose a problem and give a
> fix, or at least give users a hint at finding the cause.
>
> However, there is a
On Wed, Feb 2, 2022 at 5:35 PM Bruce Momjian wrote:
> I consider these as problems that need digging to find the cause, and
> users are usually unable to do sufficient digging, and we don't have
> time to give them instructions, so they never get a reply.
>
> Is there something we can do to
The Postgres community is great at diagnosing problems and giving users
feedback. In most cases, we can either diagnose a problem and give a
fix, or at least give users a hint at finding the cause.
However, there is a class of problems that are very hard to help with,
and I have perhaps seen an
12 matches
Mail list logo
