From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Revive line type |
Date: | 2014-05-05 17:27:40 |
Message-ID: | 20140505172740.GC17909@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2014-05-05 13:24:15 -0400, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > On 2013-10-10 02:43:20 +0000, Peter Eisentraut wrote:
> >> Revive line type
>
> > That commit missed to update pg_type.h to the changed length of the line
> > type. Patch attached.
>
> Ouch. Good thing we caught this now.
Yea. The only thing we could have done later is to allocate more memory
and waste the space ondisk :(.
I am really hoping to get pg into a state where it's sufficiently
valgrind clean that we can run a buildfarm animal under valgrind. The
newest release of valgrind helps there - e.g. some float bugs have been
worked out.
> In principle, fixing this breaks pg_upgrade'ability for anyone who was
> using the line type before (presumably by compiling with
> -DENABLE_LINE_TYPE). However, we're breaking things for them anyway by
> changing the text representation, so that's probably not worth worrying
> over.
Agreed
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-05-05 17:38:00 | pgsql: Fix pg_type.typlen for newly-revived line type. |
Previous Message | Tom Lane | 2014-05-05 17:24:15 | Re: pgsql: Revive line type |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2014-05-05 17:30:17 | Re: New and interesting replication issues with 9.2.8 sync rep |
Previous Message | Josh Berkus | 2014-05-05 17:26:24 | TABLESPACE and directory for Foreign tables? |