Re: BUG #6705: 32 bit - Mailing list pgsql-bugs

From Craig Ringer
Subject Re: BUG #6705: 32 bit
Date
Msg-id 4FE8860B.7010300@ringerc.id.au
Whole thread Raw
In response to Re: BUG #6705: 32 bit  (Dave Page <dpage@pgadmin.org>)
Responses Re: BUG #6705: 32 bit
List pgsql-bugs
On 06/25/2012 11:10 PM, Dave Page wrote:
> On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer <ringerc@ringerc.id.au> wrote:
>> Dave: Is there any chance the installers link to that page from their error
>> dialogs, or a static-and-sanitised version of it in docs? If you're ok
>> updating the installer messages I'll collect up a sanitized version that
>> doesn't link to other wiki pages (or make it clear they're external) and
>> convert it for the docs.
> We can't do clickable links in those message boxes, so I'm not sure
> how useful it'll be in practice.
Argh. I've been in the browser-based app too long, I simply forget that
URL handling isn't everywhere.

The main ones that IMO need a where-to-go-next hint are the messages
that arise when an external process step fails, like initdb, failure to
install the runtime, etc. It's /always/ necessary to ask a poster asking
for help for the installer log - and how many people don't post or ask
for help, just get stuck and confused?

--
Craig Ringer

pgsql-bugs by date:

Previous
From: Dave Page
Date:
Subject: Re: BUG #6705: 32 bit
Next
From: m.sakrejda@gmail.com
Date:
Subject: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created