Hi folks.

I successfully compiled/built pg 8.1.9 using --with-openssl on a Mac.
I modified the startup config files to enable ssl.
Server starts without problems, but when I try to require SSL from
pgAdminIII, I get "server does not support SSL".

Has anyone been able to get an SSL-enabled PG built and running on
Mac OS X (10.2.4)?

Help -- I am pulling the last hairs I have left.



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

Michael Hogarth <mahogarth@ucdavis.edu> writes:
> Has anyone been able to get an SSL-enabled PG built and running on
> Mac OS X (10.2.4)?

Dunno about 10.2.x, but it seems to work fine for me on 10.4.10.

Can you connect with psql, and does it show a startup comment like
this:

SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)

regards, tom lane

---------------------------(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

On Jul 6, 2007, at 9:57 PM, Michael Hogarth wrote:

> Hi folks.
>
> I successfully compiled/built pg 8.1.9 using --with-openssl on a Mac.
> I modified the startup config files to enable ssl.
> Server starts without problems, but when I try to require SSL from
> pgAdminIII, I get "server does not support SSL".
>
> Has anyone been able to get an SSL-enabled PG built and running on
> Mac OS X (10.2.4)?
>
> Help -- I am pulling the last hairs I have left.

This may not apply at all. When I tried to get subversion to work
with openssl, the key was to compile neon with openssl. Does any of
this use Neon?

If not, then please hit 'd' for delete....



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

Hello.
Is it possible to retrieve information about how many rows were
changed/inserted in a table that fired after statement trigger?
Thanks,

Zlatko


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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> Is it possible to retrieve information about how many rows were
> changed/inserted in a table that fired after statement trigger?

Not directly, but you can store the information from row-level
triggers and gather it at the end. See this plperl example:

http://people.planetpostgresql.org/g...007/05/30.html

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200707070745
http://biglumber.com/x/web?pk=2529DF...9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFGj30hvJuQZxSWSsgRA9iXAJ0aiS5oVbYxcY69yY0zvi g4G4eBTwCdE5ON
EYV77TeTYNSRt46fsZDfkTI=
=C7mD
-----END PGP SIGNATURE-----



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

Thank you for the answer.
At least I'm glad it is possible!
But , as I don't know Perl, could you, please, tell me how to accomplish it
in plpgsql.
Thanks,

Zlatko

----- Original Message -----
From: "Greg Sabino Mullane" <greg@turnstep.com>
To: <pgsql-general@postgresql.org>
Sent: Saturday, July 07, 2007 1:47 PM
Subject: Re: [GENERAL] How to retrieve number of rows affected, in an after
statement trigger?


>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>> Is it possible to retrieve information about how many rows were
>> changed/inserted in a table that fired after statement trigger?
>
> Not directly, but you can store the information from row-level
> triggers and gather it at the end. See this plperl example:
>
> http://people.planetpostgresql.org/g...007/05/30.html
>
> - --
> Greg Sabino Mullane greg@turnstep.com
> PGP Key: 0x14964AC8 200707070745
> http://biglumber.com/x/web?pk=2529DF...9B906714964AC8
> -----BEGIN PGP SIGNATURE-----
>
> iD8DBQFGj30hvJuQZxSWSsgRA9iXAJ0aiS5oVbYxcY69yY0zvi g4G4eBTwCdE5ON
> EYV77TeTYNSRt46fsZDfkTI=
> =C7mD
> -----END PGP SIGNATURE-----
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq