From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Victor Whiskey Yankee <victor(dot)whiskey(dot)yankee(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: could not access file "$libdir/plpgsql": No such file or directory |
Date: | 2012-05-31 05:35:17 |
Message-ID: | 28970.1338442517@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Victor Whiskey Yankee <victor(dot)whiskey(dot)yankee(at)gmail(dot)com> writes:
> Thank you for the reply... after I removed the "--disable-shared" I do see the $libdir/plpgsql.so. But I do not see
> any static libs, and "./configure" does not have an option to enable both static and shared..... so I guess it also means I cannot
> build postgress libs nor link my apps statically?
I'm a bit confused by this. There is no option to build plpgsql as a
static library, but that has nothing to do with linking your
applications. You should see static versions of the libraries that
are meant to be used client-side: libpq.a, ecpglib.a, etc.
In general, if you're looking for minimum resource footprint, it seems
to me that static libraries are not what you want anyway; you tend to
end up with N copies of the same code.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ross Boylan | 2012-05-31 06:09:49 | Re: how to call stored procedures that are writes |
Previous Message | Tom Lane | 2012-05-31 05:23:56 | Re: how to call stored procedures that are writes |