| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Thomas F(dot) O'Connell" <tfo(at)monsterlabs(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: NAMEDATALEN |
| Date: | 2001-05-10 21:04:49 |
| Message-ID: | 24865.989528689@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Thomas F. O'Connell" <tfo(at)monsterlabs(dot)com> writes:
> in src/include/postgres_ext.h, it mentions that "... databases with
> different NAMEDATALEN's cannot interoperate!", and i was wondering if
> included when altering NAMEDATALEN for a database that already has data
> even if performing a pg_dump on it.
Dump, recompile, initdb, reload should work. Be aware however that
NAMEDATALEN is visible to clients (in particular, in libpq's
datastructure for Notify results), so you may have binary-compatibility
problems if you neglect to recompile your clients too. I suspect that
is what the comment is really referring to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-10 21:22:07 | Re: Re: Query not using index |
| Previous Message | David Wheeler | 2001-05-10 20:58:30 | Re: Custom Constraint |