Re: Bytea as C string in pg_convert?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bytea as C string in pg_convert?
Date: 2007-09-24 16:12:25
Message-ID: 14954.1190650345@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> Hmm. One suggestion would be to have an internal function declared
>> as taking and returning "struct varlena *", with a comment saying that
>> we depend on text and bytea both being compatible with this. All three
>> SQL-visible functions are then thin wrappers around that.

> Doesn't strike me as much of an advance, to be honest.

As you wish, but at least a comment noting that these functions are
relying on binary compatibility of text and bytea would be a good idea.

> My current top priority is fixing the MSVC build .bat files like Magnus
> wants, which will take a bit of time.

If you are intending to make the buildfarm use the perl scripts, then
this should definitely be high priority --- we don't want the farm
testing some other build process than what ordinary users will use.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-09-24 16:40:06 Re: autovacuum launcher eating too much CPU
Previous Message Andrew Dunstan 2007-09-24 16:01:47 Re: Bytea as C string in pg_convert?