rum index supported on pg13?

2020-10-08 Thread John the Scott
will rum index from postgrespro be supported in pg13?
numerous errors occur when compiling rum in pg13 and
no replies from github.  the differences from pg12
to pg13 seem to be significant

 https://github.com/postgrespro/rum

thanks for such a brilliant extension.
perhaps i should jump in and help.

-john


-- 
Fast is fine, But accuracy is final.
You must learn to be slow in a hurry.
- Wyatt Earp




Re: rum index supported on pg13?

2020-10-12 Thread John the Scott
No, instead i posted the compile errors.

I am still new to github protocol, so i was not sure
if asking about longer term support of rum was appropriate for
the github issues posting.

the differences between pg12 and pg13 seem considerable.
our internal use of rum has been spectacularly successful,
we may be able to justify resources to fixing the compile issues with pg13,
but the effort will be considerable.

-john

On Sun, Oct 11, 2020 at 7:16 PM Michael Paquier  wrote:
>
> On Thu, Oct 08, 2020 at 09:29:31PM -0500, John the Scott wrote:
> > will rum index from postgrespro be supported in pg13?
> > numerous errors occur when compiling rum in pg13 and
> > no replies from github.  the differences from pg12
> > to pg13 seem to be significant
> >
> >  https://github.com/postgrespro/rum
>
> Did you ask directly this question to the authors of the extension on
> the page of the project you are quoting above?
> --
> Michael



-- 
Fast is fine, But accuracy is final.
You must learn to be slow in a hurry.
- Wyatt Earp




Re: rum index supported on pg13?

2020-10-21 Thread John the Scott
excellent.  pg13+rum passes all our tests.

thanks-john

On Thu, Oct 15, 2020 at 3:18 AM Teodor Sigaev  wrote:
>
> Done, thank you
>
> On 14.10.2020 19:30, Devrim Gündüz wrote:
> >
> > Hi Teodor,
> >
> > On Wed, 2020-10-14 at 18:49 +0300, Teodor Sigaev wrote:
> >> Thank you, fixed and published.
> >
> > Can you please release a new tarball? We need that to build the RPM
> > packages. I'm still seeing 1.3.6 as the latest version.
> >
> > Thanks!
> >
> > Regards,
> >
>
> --
> Teodor Sigaev  E-mail: teo...@sigaev.ru
>WWW: http://www.sigaev.ru/



-- 
Fast is fine, But accuracy is final.
You must learn to be slow in a hurry.
- Wyatt Earp




Re: Planet Postgres and the curse of AI

2024-08-22 Thread John the Scott
> Posts should be technically and factually correct

agreed and period.  no need qualify how the nonsense was created.

-john

On Thu, Aug 22, 2024 at 4:13 PM Robert Treat  wrote:
>
> On Tue, Aug 20, 2024 at 8:33 AM Greg Sabino Mullane  
> wrote:
> >
> > On Tue, Jul 23, 2024 at 12:45 PM Avinash Vallarapu 
> >  wrote:
> >>
> >> However, I do agree with Lawrence that it is impossible to prove whether 
> >> it is written by AI or a human.
> >> AI can make mistakes and it might mistakenly point out that a blog is 
> >> written by AI (which I know is difficult to implement).
> >
> >
> > Right - I am not interested in "proving" things, but I think a policy to 
> > discourage overuse of AI is warranted.
> >
> >> People may also use AI generated Images in their blogs, and they may be 
> >> meaningful for their article.
> >> Is it only the content or also the images ?  It might get too complicated 
> >> while implementing some rules.
> >
> >
> > Only the content, the images are perfectly fine. Even expected, these days.
> >
> >>
> >> Ultimately, Humans do make mistakes and we shouldn't discourage people 
> >> assuming it is AI that made that mistake.
> >
> >
> > Humans make mistakes. AI confidently hallucinates.
> >
>
> I think this is a key point, and one that we could focus on for
> purposes of discouragement. Ie.  "Blogs that are found to repeatedly
> post incorrect information and/or AI style hallucinations may be
> restricted from contributing to the planet postgres feed. This will be
> determined on a case by case basis."  While it is likely impossible to
> come up with a set of rules that will satisfy some of the more
> legalistic folks among us, this would be a simple warning that would
> at least encourage folks to make sure they aren't posting bad
> information and leave a door open for enforcement if needed. And yes,
> this assumes that the folks running planet will enforce if needed,
> though I don't think it requires heavy policing at this point.
>
> Robert Treat
> https://xzilla.net
>
>


-- 
Fast is fine, But accuracy is final.
You must learn to be slow in a hurry.
- Wyatt Earp