Thank you.. I didn't know about race condition.. Shame on me :)
> If you're using PostgreSQL 8.0 or later then you can get the sequence
> name with the pg_get_serial_sequence() function:
Is there any way how to do that (or add this function) in 7.3.x ?
Best regards,
Lada '
lass ?
2. make code reading 'sequence names' live. I looked around pg_class but I
am not sure which relation between reltype,relfilenode,reltoastrelid are
proper ones... So, how to get 'sequence name' by its 'table name' ? Name of
sequence and table are not related (w
7.4.x and try
all SQL's again. Thank you :)
Please, do you know if exists some 'up-to-date' doc about curret state of
planner ? I didn't found something like that.
Best regards,
Lada 'Ray' Lostak
Un
t;ID in (1,2,3...)" with 1500 terms is still 6x
faster rather subselect I really can't get it :)
I understand to output (which corespond with real times) - but don't have
clue, why it's soo differnet. I expect results to be 'similar'. Small
tables, 'fast'
doing will be used commerically. And
I think, this is general problem, which every bigger system have to solve.
Sooner or later.
I fully agree with you, that locking is not a way. But is there any other
'more automatized' way than take care of row versions by ourself ?
But before contacting
done in 'longer' time - e.g.
hour or so (it take hour to change all datas together) and within various
database connections.
Thx
Best regards,
Lada 'Ray' Lostak
Unreal64 Develop group
http://www.orcave.com
http://www.unreal64.net
-
urces, talking about this
problem. I didn't find anything usefull around.
Thank you again,
Best regards,
Lada 'Ray' Lostak
Unreal64 Develop group
http://www.orcave.com
http://www.unreal64.net
--
In the 1960s yo
on should be possibility to 'begin' transaction, 'store'
somehow on server, and next time, instead of begin new transaction return to
stored one. Transactions solves all these problems, but they don't work
across various/multiple connections
Any ideas/references
yet released)
contain small chapter / paragraph at LO about this. If someone is new to PG
(like me), there is no enough information about 'using' LO.
Thank you for corrections and comments about LO/columns binary storing.
I hope this email belong to general discussion. If no, I am sorry and
But the time coresponds
What can I do (or where is some document regarding this topic ?) speed up
PgSql ? I really think, half second for selecting ~100 rows from ~600 rows
table it pretty slow. Commodore 64 (1 mHz 6510) will do it faster :)
Any hints ?
Thanks,
Best regards,
Lada 'Ray&#x
14,20,12,40,34,... it will be fine.
But something like 50, 500, 2000 makes me crazy
I have added 'log' - part of pgsql log coresponding to above SQL.
Feel free to have any Q about sysconfig/programs config.
And sorry again if I miss something.
Thank yo
11 matches
Mail list logo
