From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Planet Postgres and the curse of AI |
Date: | 2024-07-18 12:31:23 |
Message-ID: | aae1616a4ebf8eb129b2510c75d4c335a028d623.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I wrote:
> On Wed, 2024-07-17 at 13:21 -0400, Greg Sabino Mullane wrote:
> > I've been noticing a growing trend of blog posts written mostly, if not entirely, with AI
> > (aka LLMs, ChatGPT, etc.). I'm not sure where to raise this issue. I considered a blog post,
> > but this mailing list seemed a better forum to generate a discussion.
> >
> > [...]
> >
> > Do we need a policy or a guideline for Planet Postgres? I don't know. It can be a gray line.
> > Obviously spelling and grammar checking is quite okay, and making up random GUCs is not,
> > but the middle bit is very hazy. (Human) thoughts welcome.
>
> As someone who writes blogs and occasionally browses Planet Postgres, this has not
> struck me as a major problem. I just scrolled through it and nothing stood out to
> me - perhaps I am too naïve.
Seems like I *was* naïve - Álvaro has pointed me to a juicy example off-list.
Still, I wouldn't make a policy specifically against AI generated content. That is
hard to prove, and it misses the core of the problem. The real problem is low-level,
counterfactual content, be it generated by an AI or not.
Perhaps there could be a way to report misleading, bad content and a policy that says
that you can be banned if you repeatedly write grossly misleading and counterfactual
content. Stuff like "to improve performance, set fast_mode = on and restart the database".
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | KK CHN | 2024-07-18 13:19:07 | Re: PgbackRest and EDB Query |
Previous Message | Francisco Olarte | 2024-07-18 11:53:00 | Re: Re. Select with where condition times out |