pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: josh@agliodbs.com
Cc: pgsql-docs@postgresql.org
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
Date: Sat, 17 Nov 2007 13:01:01 -0800
Message-ID: <473F568D.2060308@commandprompt.com> (raw)
In-Reply-To: <20609.1195332773@sss.pgh.pa.us>
References: <200711171134.lAHBYnt11239@momjian.us>
	<473F4C26.3090907@commandprompt.com>
	<20609.1195332773@sss.pgh.pa.us>

Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> Honestly, I think you are underestimating this problem.
> 

> I fail to see why this is a major problem; and merely asserting that
> it is one isn't going to change my mind.  Can you point to something
> like a major application that will be broken and can't easily be fixed?

SQL-Ledger/LedgerSMB

What I find interesting is that I (and Josh) are getting push back and 
all we are trying to do is be a little louder about the change.


Joshua D. Drake

> 
> 			regards, tom lane
> 




view thread (37+ messages)  latest in thread

Message-ID: <473F568D.2060308@commandprompt.com>
Permalink:  ../473F568D.2060308@commandprompt.com/
Also on:    postgresql.org/message-id/473F568D.2060308@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: jd@commandprompt.com, tgl@sss.pgh.pa.us, bruce@momjian.us, josh@agliodbs.com
  Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
  In-Reply-To: <473F568D.2060308@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox