Re: Bugs status tracking

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: VASUKI M <vasukim1992002(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Bugs status tracking
Date: 2025-02-17 14:31:10
Message-ID: CAKAnmm++pBZBPsLSTNX0t-8rEq0bQ=uYNgscsVs3z2hHSDv0qg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 17, 2025 at 2:47 AM VASUKI M <vasukim1992002(at)gmail(dot)com> wrote:

> Please can u tell whether it is ok or not or do we need to change anything
> ,as of now the community is bigger and we have people to track the status
> so please give suggestions or corrections.
>

All of our data is public and free to use, so you are welcome to do with it
what you want.

I would suggest just creating a proof of concept and let's see what it
looks like. Nobody is going to officially bless it beforehand. Being able
to see and critique an actual workflow is invaluable.

Be warned that no matter what you come up with, not everyone will be happy
with it. That's the nature of things, so don't be discouraged.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-02-17 15:09:04 BUG #18816: pg16 requires perl 5.14+ but is not documented
Previous Message Raghu Dev Ramaiah 2025-02-17 12:19:04 issue with PSQL 17.1 on Suse 15 Linux SP6