On Fri, Feb 24, 2006 at 02:57:19PM -0500, Bruce Momjian wrote:
> Yea, that is probably the best you can do currently, but it is pretty
> ugly. We have PQserverVersion() in libpq for use by clients, which
> does:
>
> conn->sversion = (100 * vmaj + vmin) * 100 + vrev;
>
> Perhaps we sh
Joe Conway wrote:
> Martijn van Oosterhout wrote:
> > On Thu, Feb 16, 2006 at 08:36:34PM +0100, Pavel Stehule wrote:
> >>I use counstruct_md_array function in my Orafunc module. CVS version has
> >>diff def now. I am findig way for simple solution of maintaince source code
> >>for both version. I
Martijn van Oosterhout wrote:
On Thu, Feb 16, 2006 at 08:36:34PM +0100, Pavel Stehule wrote:
I use counstruct_md_array function in my Orafunc module. CVS version has
diff def now. I am findig way for simple solution of maintaince source code
for both version. I have PG_VERSION variable, but it'
On Thu, Feb 16, 2006 at 08:36:34PM +0100, Pavel Stehule wrote:
> Hello
>
> I use counstruct_md_array function in my Orafunc module. CVS version has
> diff def now. I am findig way for simple solution of maintaince source code
> for both version. I have PG_VERSION variable, but it's unusable. Is
Hello
I use counstruct_md_array function in my Orafunc module. CVS version has
diff def now. I am findig way for simple solution of maintaince source code
for both version. I have PG_VERSION variable, but it's unusable. Is there
way for contrib's autors differentiate PostgreSQL versions? I don
