hi all,
I read the code that it seems easy for the cursor in plpgsql to return
ROW_COUNT after
MOVE LAST etc. The SPI_processed variable already there, but didn't put
it into estate
structure, any reason for that?
thanks and best regards
-laser
--
Sent via pgsql-hackers mailing list (pgsql
that? Any hints will be great
appreciated!
thanks and best regards
-laser
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
switch explicit), but I think
that might be break someone's application somewhere. :(
regards laser
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
into it. then build a partial index
on it:
create index partial_idx on partial_idx_t (id) where id =1 and id =
20;
my purpose is to see if I could use partial index while doing count(*),
it seems the index being used after a 'set enable_seqscan=off':
laser=# explain analyze select count
,
but the old Makefile is ok. don't know why, if put up there, then you can
generate other format without problem.
Thanks Regards
Laser Henry
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
to
$PGDIR/share/pgaccess/lib/languages/ for current CVS version,
and $PGDIR/pgaccess/lib/languages/ for 7.0*
BTW: I havn't got the tools to translate it to BIG5 encoding, is there
anybody to to it?
Regards
Laser
chinese_gb.gz
appropriate. There are several encodings for Chinese including
GB(EUC-CN), Big5, EUC-TW. At least we should be able to distinguish
them. What about "chinese(GB)" or whatever?
Renamed to chinese-gb.
I think chinese-gb is ok, thanks!
Regards
Laser
