Re: Re[2]: BUG #15626: Incorrect version number shown in BigSQL installation

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Guy Rouillier <guy(dot)rouillier(at)gmail(dot)com>
Cc: Pavlo Golub <pavlo(dot)golub(at)cybertec(dot)at>, PG Bug reporting form <noreply(at)postgresql(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Re[2]: BUG #15626: Incorrect version number shown in BigSQL installation
Date: 2019-02-13 12:57:03
Message-ID: CA+bJJbx8kHejfeefLhLFW=AQbYG6bjjLRjB64qKRuqVRHiq1oQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Feb 13, 2019 at 6:00 AM Guy Rouillier <guy(dot)rouillier(at)gmail(dot)com> wrote:
> At the very least, the PostgreSQL site should provide links for where to report bugs for third-party components. Expecting individuals to search for it themselves is asking quite a bit.

BigSql is not a postgresql 3rd party component. They use postgres. So
postgres has no control on what they do.

Bigsql can, and probably does, report it uses postgres and direct you
here for bugs related to it, like "I've found this sql misbehaves,
using bigsql v xx", but not the other way.

Francisco Olarte.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-02-13 13:47:59 BUG #15634: extension missing
Previous Message Amit Langote 2019-02-13 09:33:05 Re: BUG #15623: Inconsistent use of default for updatable view