Re: generic pseudotype IO functions?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: generic pseudotype IO functions?
Date: 2014-01-06 16:56:28
Message-ID: 5522.1389027388@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> I think I am less concerned about pseudotypes.c than about bloating
> pg_proc.h even further and about the annoyance of editing it - but I
> guess that should rather be fixed by storing it in a more sensible
> format at some point...

Yeah, getting rid of a dozen pseudotype I/O functions is hardly going
to reduce the PITA factor of editing pg_proc.h. It's interesting to
think about moving all those DATA() macros into some more-maintainable
format --- I'm not sure what it should be exactly, but I think something
that can insert plausible defaults for omitted columns would be a big help
for pg_proc and maybe some of the other catalogs too.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2014-01-06 17:12:03 Re: In-core regression tests for replication, cascading, archiving, PITR, etc. Michael Paquier
Previous Message Andres Freund 2014-01-06 16:47:57 Re: ERROR: missing chunk number 0 for toast value