Extra information in pg_dump
Adrian Klaver
aklaver at comcast.net
Tue May 23 19:43:07 UTC 2006
On Tuesday 23 May 2006 09:35 am, James William Pye wrote:
> On Tue, May 23, 2006 at 07:49:24AM +0200, Florian Weimer wrote:
> > * Adrian Klaver:
> > > I did a plain text dump of a database I was working on and found the
> > > following. The first function was created against PostgresPy. The
> > > second function is the same but created against plpythonu. Any clues as
> > > what all the escape sequences are for?
> >
> > I haven't checked to be sure, but it looks like Python bytecode (the
> > thing normally stored in .pyc files).
>
> That's right. This is actually a surprise to me. I didn't know(or forgot)
> you could explicitly specify the probin field in CREATE FUNCTION.
>
> This is unlikely to cause any trouble as the source is unconditionally
> compiled on CREATE. Of course, this means that this dumped bytecode is
> useless noise.
Actually when I tried to load this function into the database it complained
about the duplicate information. Leaving the byte code in is going to cause
problems in the dump-restore cycle.
Thank you,
--
Adrian Klaver
aklaver at comcast.net
More information about the Python-general
mailing list