Re: BUG #16509: Unable to change from 32 bit to 64 bit

From: Pierre Mantha <thecobv(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16509: Unable to change from 32 bit to 64 bit
Date: 2020-06-25 17:03:09
Message-ID: CAJyGEvWiSm5fUUUb4w2z9J5tFZUDN4p=S=6J7gniKuiPVnmj7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks, I'll check it out.

Pierre

* Pierre Mantha CEO*
Senior Certified & Authorized Spire Partner
Developer of SPOKE4Spire Landed Cost Calculator
Developer of SPOKE4Spire DataTools
Senior Certified Essentials Consultant
Senior Certified Sage BusinessVision Consultant

* t.h.e. & COMPANY*
Direct Line: (647) 966-3566
thecobv(at)gmail(dot)com · spoke4spire.com <http://www.spoke4spire.com>
* barcodeapps.com <http://www.barcodeapps.com/> · **swiftcount.com
<http://www.swiftcount.com/>*

*****NEW**** SPOKE4Spire Landed Cost Calculator - Quick Overview*
https://youtu.be/2F3gsIRl3T8
**** Coming 2020 SPOKE4Spire **DataTools*

On Thu, Jun 25, 2020 at 10:52 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> > On 25 Jun 2020, at 16:31, Pierre Mantha <thecobv(at)gmail(dot)com> wrote:
>
> > Well that was a complete waste of time.
>
> That's an odd way of showing appreciation when people try to help you with
> free
> software support.
>
> > In that link and the subsequent links there is absolutely no specific
> area to report a bug.
> > You click on bugs and it gives you a list - impressive but useless.
>
> The referenced page has a direct link to adding a new bug in the issue
> tracker:
>
> https://redmine.postgresql.org/projects/pgadmin4/issues/new
>
> ..as well as a link to the page for the support email list which has a
> detailed
> section on the information to include in a bugreport:
>
> https://www.pgadmin.org/support/list/
>
> Either of those two is fine to use AFAICT (I'm not affiliated with the
> pgadmin
> project), and both should work with the postgresql.org community account
> that
> you used for filing the initial bugreport.
>
> cheers ./daniel

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-06-25 17:40:04 BUG #16511: Using '= all ( )' with empty table returns true
Previous Message Tom Lane 2020-06-25 15:52:55 Re: Bug: Postgresql with Postgis: Different result in coordinate conversion NAV4 <=> WGS84 in Linux and Windows