Thread
-
Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!
Tom Lane <tgl@sss.pgh.pa.us> — 1998-11-06T18:45:13Z
Constantin Teodorescu <teo@flex.ro> writes: > [root@teo libpgtcl]# ldd libpgtcl.so.2.0 > libcrypt.so.1 => /lib/libcrypt.so.1 (0x40014000) > libc.so.6 => /lib/libc.so.6 (0x40041000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000) > [root@teo libpgtcl]# ldd ../libpq/libpq.so.2.0 > statically linked Well, that's pretty interesting. Evidently you were able to persuade the linker to dynamically link libpgtcl.so to libcrypt.so, but the patch I suggested did *not* persuade the linker to dynamically link libpq.so to libcrypt.so. Just exactly what change did you make in libpgtcl's Makefile, anyway? I assumed it was simply adding -lcrypt, but now I am not so sure. It's also curious that libpq.so is not showing any dynamic dependency on libc. I think we must have the wrong linker options for libpq. > [root@teo libpgtcl]# vdir ../libpq/libpq.so.2.0 > -rwxr-xr-x 1 root root 50014 Nov 6 10:08 > ../libpq/libpq.so.2.0 > [root@teo libpgtcl]# vdir libpgtcl.so.2.0 > -rwxr-xr-x 1 root root 64725 Nov 6 10:19 libpgtcl.so.2.0 And we also need to figure out why the linker is including libpq.a into libpgtcl.so, instead of creating a dynamic link from libpgtcl.so to libpq.so like it did for libcrypt and libc. (BTW, do you have a libcrypt.a in /lib, or just libcrypt.so?) It seems clear from your ldd results that your machine is capable of doing the right thing, but we aren't invoking the linker with the right options. Where I want to get to is: libpgtcl.so: dynamic dependency on libpq.so (and libc of course) libpq.so: dynamic dependency on libcrypt.so (and libc of course) It might be worth extracting the part of the "make all" log that shows what commands are being used to build each of these libraries. regards, tom lane
-
Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!
Constantin Teodorescu <teo@flex.ro> — 1998-11-07T08:20:25Z
Tom Lane wrote: > > Constantin Teodorescu <teo@flex.ro> writes: > > [root@teo libpgtcl]# ldd libpgtcl.so.2.0 > > libcrypt.so.1 => /lib/libcrypt.so.1 (0x40014000) > > libc.so.6 => /lib/libc.so.6 (0x40041000) > > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000) > > > [root@teo libpgtcl]# ldd ../libpq/libpq.so.2.0 > > statically linked > > Well, that's pretty interesting. Evidently you were able to persuade > the linker to dynamically link libpgtcl.so to libcrypt.so, but the patch > I suggested did *not* persuade the linker to dynamically link libpq.so > to libcrypt.so. The patch that you send me I have applied ONLY to Makefile.in from src/interfaces/libpgtcl directory. Should I apply it to Makefile.in from src/interfaces/libpq directory ? > Just exactly what change did you make in libpgtcl's > Makefile, anyway? I assumed it was simply adding -lcrypt, but now I > am not so sure. Yes. Only add -lcrypt > And we also need to figure out why the linker is including libpq.a into > libpgtcl.so, instead of creating a dynamic link from libpgtcl.so to > libpq.so like it did for libcrypt and libc. > > (BTW, do you have a libcrypt.a in /lib, or just libcrypt.so?) in /usr/lib libcrypt.a and libcrypt.so in /lib/libcrypt.so -- Constantin Teodorescu FLEX Consulting Braila, ROMANIA
-
Re: [INTERFACES] limiting the rows selected in postgresql
Sergio A. Kessler <ser@perio.unlp.edu.ar> — 1998-11-07T16:39:27Z
Sferacarta Software <sferac@bo.nettuno.it> el día Mon, 9 Nov 1998 14:33:06 +0100, escribió: >Hello Radhakrishnan, > >lunedì, 9 novembre 98, you wrote: > > >RCV> how can i limit the number of rows obtained from a select statement >RCV> in postgreSQL to say, 10 rows while the select condition actually >RCV> matches more than that. in oracle we can use the ROW_NUM variable >RCV> for this purpose but now i met such an issue with postgreSQL > >On v6.4 you can specify a limit for queries as: > >set QUERY_LIMIT TO '10'; >To have only the first 10 rows from a select; this will limit _all_ the querys, right ? wich is not very flexible. I can't do something like select * from news order by news_date limit 10 ? Sergio
-
limiting the rows selected in postgresql
RADHAKRISHNAN C V <cvr@md2.vsnl.net.in> — 1998-11-09T12:52:58Z
how can i limit the number of rows obtained from a select statement in postgreSQL to say, 10 rows while the select condition actually matches more than that. in oracle we can use the ROW_NUM variable for this purpose but now i met such an issue with postgreSQL thanks in advance CV Radhakrishnan http://www.river-valley.com
-
Re: [INTERFACES] limiting the rows selected in postgresql
jose' soares <sferac@bo.nettuno.it> — 1998-11-09T13:33:06Z
Hello Radhakrishnan, lunedì, 9 novembre 98, you wrote: RCV> how can i limit the number of rows obtained from a select statement RCV> in postgreSQL to say, 10 rows while the select condition actually RCV> matches more than that. in oracle we can use the ROW_NUM variable RCV> for this purpose but now i met such an issue with postgreSQL On v6.4 you can specify a limit for queries as: set QUERY_LIMIT TO '10'; To have only the first 10 rows from a select; -Jose'-
-
Re: [INTERFACES] limiting the rows selected in postgresql
Oleg Bartunov <oleg@sai.msu.su> — 1998-11-09T20:27:49Z
On Sat, 7 Nov 1998, Sergio wrote: > Date: Sat, 7 Nov 1998 13:39:27 -0300 > From: Sergio <ser@perio.unlp.edu.ar> > To: pgsql-interfaces@postgreSQL.org > Subject: Re: [INTERFACES] limiting the rows selected in postgresql > > Sferacarta Software <sferac@bo.nettuno.it> el dМa Mon, 9 Nov 1998 14:33:06 > +0100, escribiС: > > >Hello Radhakrishnan, > > > >lunedЛ, 9 novembre 98, you wrote: > > > > > >RCV> how can i limit the number of rows obtained from a select statement > >RCV> in postgreSQL to say, 10 rows while the select condition actually > >RCV> matches more than that. in oracle we can use the ROW_NUM variable > >RCV> for this purpose but now i met such an issue with postgreSQL > > > >On v6.4 you can specify a limit for queries as: > > > >set QUERY_LIMIT TO '10'; > >To have only the first 10 rows from a select; > > this will limit _all_ the querys, right ? > wich is not very flexible. > > I can't do something like > > select * from news order by news_date limit 10 > > ? Sergio, be patient. Jan Wieck is working on patch for support LIMIT in select query. I'm using his patch (trial 2) with 6.4 and it works great for me. With this patch you can limit output using LIMIT offset,count statement. Hope, this patch will come to 6.4.1. Regards, Oleg PS. Browse hackers mailing list for last month to read discussion on this subject. > > Sergio > > _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 -
Re: [INTERFACES] limiting the rows selected in postgresql
A James Lewis <james@vrtx.net> — 1998-11-09T22:06:11Z
I did this with:- declare tmp cursor for select * from table;fetch forward 10 in tmp; But if someone else has a better way, please let me know.... On Sat, 7 Nov 1998, Sergio wrote: > Sferacarta Software <sferac@bo.nettuno.it> el da Mon, 9 Nov 1998 14:33:06 > +0100, escribi: > > >Hello Radhakrishnan, > > > >luned, 9 novembre 98, you wrote: > > > > > >RCV> how can i limit the number of rows obtained from a select statement > >RCV> in postgreSQL to say, 10 rows while the select condition actually > >RCV> matches more than that. in oracle we can use the ROW_NUM variable > >RCV> for this purpose but now i met such an issue with postgreSQL > > > >On v6.4 you can specify a limit for queries as: > > > >set QUERY_LIMIT TO '10'; > >To have only the first 10 rows from a select; > > this will limit _all_ the querys, right ? > wich is not very flexible. > > I can't do something like > > select * from news order by news_date limit 10 > > ? > > Sergio > > James (james@linuxrocks.co.uk) Vortex Internet My Windows unders~1 long filena~1, and yours?