From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Lane <slane@soliantconsulting.com>
Cc: pgsql-admin@postgresql.org, Jamie Thomas <jthomas@soliantconsulting.com>
Subject: Re: PG 7.2 varchar change
Date: Fri, 13 Aug 2004 14:58:36 -0400
Message-ID: <25891.1092423516@sss.pgh.pa.us> (raw)
In-Reply-To: <BD41AE99.18DBE%slane@soliantconsulting.com>
References: <BD41AE99.18DBE%slane@soliantconsulting.com>
Steve Lane <slane@soliantconsulting.com> writes:
> Thanks, Tom, that's very helpful. One more clarification: if the underlying
> column has no express length limit (for example, it was defined as type
> 'text'), is this issue moot?
Right, it only applies to specifically-declared length limits.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, slane@soliantconsulting.com, jthomas@soliantconsulting.com
Subject: Re: PG 7.2 varchar change
In-Reply-To: <25891.1092423516@sss.pgh.pa.us>
References: <BD41AE99.18DBE%slane@soliantconsulting.com> <25891.1092423516@sss.pgh.pa.us>
* 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