Chris Browne wrote:
> bruce@momjian.us (Bruce Momjian) writes:
> > Here are the open items for 8.2:
> >
> > http://momjian.postgresql.org/cgi-bin/pgopenitems
> >
> > This list will be continually updated until we release 8.2.
>
> I've got suggested patches for my item (e.g. - --with-openssl causing
> contrib stuff to break on AIX); a couple of instances of:
>
> SHLIB_LINK = $(libpq) $(LIBS)
>
> in contrib/dblink/Makefile and contrib/sslinfo seem to do the trick.
> I'm not sure of adverse effects for others, so that's only speculative
> at this point...

My guess is that sslinfo needs it because of the use of the SSL
libraries. I would guess any of the other /contrib modules would need
similar changes. Can you do a 'make' at the top of the contrib tree and
see what fails?

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Bruce Momjian <bruce@momjian.us> writes:
> Chris Browne wrote:
>> I've got suggested patches for my item (e.g. - --with-openssl causing
>> contrib stuff to break on AIX); a couple of instances of:
>>
>> SHLIB_LINK = $(libpq) $(LIBS)
>>
>> in contrib/dblink/Makefile and contrib/sslinfo seem to do the trick.
>> I'm not sure of adverse effects for others, so that's only speculative
>> at this point...

> My guess is that sslinfo needs it because of the use of the SSL
> libraries.

I just added $(LIBS) to sslinfo's Makefile to fix its build failure on
Darwin. (I see no reason why libpq should be involved there, though.)
I'm unclear on why AIX would need more than Darwin does to get dblink
to build.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Centuries ago, Nostradamus foresaw when tgl@sss.pgh.pa.us (Tom Lane) would write:
> Bruce Momjian <bruce@momjian.us> writes:
>> Chris Browne wrote:
>>> I've got suggested patches for my item (e.g. - --with-openssl causing
>>> contrib stuff to break on AIX); a couple of instances of:
>>>
>>> SHLIB_LINK = $(libpq) $(LIBS)
>>>
>>> in contrib/dblink/Makefile and contrib/sslinfo seem to do the trick.
>>> I'm not sure of adverse effects for others, so that's only speculative
>>> at this point...
>
>> My guess is that sslinfo needs it because of the use of the SSL
>> libraries.
>
> I just added $(LIBS) to sslinfo's Makefile to fix its build failure on
> Darwin. (I see no reason why libpq should be involved there,
> though.)

> I'm unclear on why AIX would need more than Darwin does to get dblink
> to build.

In the case of dblink/Makefile, it started as

SHLIB_LINK = $(libpq)

which need to be augmented to:

SHLIB_LINK = $(libpq) $(LIBS)

When I saw the same errors pop up with sslinfo, there was no
SHLIB_LINK definition, so went to:

SHLIB_LINK = $(libpq) $(LIBS)

It's entirely possible that
SHLIB_LINK = $(LIBS)
is sufficient.
--
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','gmail.com').
http://linuxfinances.info/info/spreadsheets.html
"We defeated the enemy with teamwork and the hammer of not bickering."
-- The Shoveller, Mystery Men

--On Montag, September 04, 2006 23:58:35 -0400 Tom Lane <tgl@sss.pgh.pa.us>
wrote:

> Updatable views are likewise dead --- we don't have a credible patch or
> any short-term path to get one. I hope to see both of these items land
> early in the 8.3 devel cycle, but for 8.2, nyet.

Yeah, i don't had the time to get to it the last days and to fix all
outstanding issues,
sorry for that. Regarding to the complexity of all required work that needs
to be done, 8.3
is the better choice, indeed.

--
Thanks

Bernd

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Am Dienstag, 5. September 2006 05:58 schrieb Tom Lane:
> A couple of recently discussed FE/BE protocol issues are: not storing a
> plan at all for unnamed-statement cases, and thus allowing bind
> parameters to be treated as constants; allowing parameter types to go
> unresolved rather than throwing an error. Perhaps it's too late to
> consider these for 8.2, but they seem no more invasive than some other
> items on the open-issues list.

Do we have a patch for that today?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Am Dienstag, 5. September 2006 03:07 schrieb Bruce Momjian:
> Here are the open items for 8.2:
>
> http://momjian.postgresql.org/cgi-bin/pgopenitems

This host seems to be offline. What about using the wiki?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hello,

On Wed, 2006-09-06 at 13:04 +0200, Peter Eisentraut wrote:
> > http://momjian.postgresql.org/cgi-bin/pgopenitems
>
> This host seems to be offline.

It is suffering from a DNS problem.

> What about using the wiki?

Wiki has the same problem, too.

Regards,
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBE/q5/pme12CBXnxERAvc1AJ9vp9PxFZYryKUS69F3RElvk7H/dACfabIQ
48fDwqPZF//TTLl8gp2qIYQ=
=Ygfy
-----END PGP SIGNATURE-----

> > Here are the open items for 8.2:
> >
> > http://momjian.postgresql.org/cgi-bin/pgopenitems
>
> This host seems to be offline. What about using the wiki?

The problem is with the postgresql.org DNS servers. Something weird is
afoot around the hub.org nameservers, from what I can tell. Servers seem
to be dropping off one by one as TTLs expire.

//Magnus


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Martha Stewart called it a Good Thing when mha@sollentuna.net ("Magnus Hagander") wrote:
>> > Here are the open items for 8.2:
>> >
>> > http://momjian.postgresql.org/cgi-bin/pgopenitems
>>
>> This host seems to be offline. What about using the wiki?
>
> The problem is with the postgresql.org DNS servers. Something weird is
> afoot around the hub.org nameservers, from what I can tell. Servers seem
> to be dropping off one by one as TTLs expire.

Apparently Marc is back; he recently had a question about reordering
IP addresses on pgsql.sql, which suggests some sort of DNS maintenance
being up.

Hopefully this is a matter of things getting a little worse before
they get more comprehensively fixed. I hope...
--
let name="cbbrowne" and tld="gmail.com" in name ^ "@" ^ tld;;
http://linuxdatabases.info/info/spreadsheets.html
"Look, would it save you all this bother if I just gave up and went
mad now?" -- Arthur Dent

Peter Eisentraut <peter_e@gmx.net> writes:
> Am Dienstag, 5. September 2006 05:58 schrieb Tom Lane:
>> A couple of recently discussed FE/BE protocol issues are: not storing a
>> plan at all for unnamed-statement cases, and thus allowing bind
>> parameters to be treated as constants; allowing parameter types to go
>> unresolved rather than throwing an error. Perhaps it's too late to
>> consider these for 8.2, but they seem no more invasive than some other
>> items on the open-issues list.

> Do we have a patch for that today?

We could have a patch for the first one today --- I was thinking about
it last night and intending to code it today. The second one is merely
a matter of removing an error check that exists now; the question really
is do people want that behavior. (I asked that on the jdbc list and got
zero response, so actually I was thinking that it was a dead issue; but
as long as it's on the open-items list we ought to discuss it.)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org