Re: [HACKERS] random access - bytea

2003-10-26 Thread Dennis Bjorklund
On Sun, 26 Oct 2003, Christopher Kings-Lynne wrote: > > to find the row and then to perform the substr. An open command can > > be optimized a lot more, for example to cache entries that have been > > opened so that it's fast to read the next 1kb or whatever you want. > > It's an index scan, so

Re: [HACKERS] random access - bytea

2003-10-26 Thread Dennis Bjorklund
On Sun, 26 Oct 2003, Hannu Krosing wrote: > I brought it up once and Tom answered that TOAST tables are not > transaction aware, so you can't update just some parts of toasted > entities - you must always write the whole fields. So this will not be > just an api change. Yes, the blocks (or what o

Re: [HACKERS] random access - bytea

2003-10-26 Thread Hannu Krosing
Dennis Bjorklund kirjutas P, 26.10.2003 kell 07:30: > On Sat, 25 Oct 2003, Joe Conway wrote: > > > That will modify the bytea column so that it is stored uncompressed in > > the TOAST table. > > > > Now, simply use substr() to grab any random chunk: > > SELECT substr(foo_bytea, 2, 100) from

Re: [HACKERS] random access - bytea

2003-10-26 Thread Christopher Kings-Lynne
This would imply that every little read would have to do a scan on a table to find the row and then to perform the substr. An open command can be optimized a lot more, for example to cache entries that have been opened so that it's fast to read the next 1kb or whatever you want. It's an index sc

Re: [HACKERS] random access - bytea

2003-10-25 Thread Dennis Bjorklund
On Sat, 25 Oct 2003, Joe Conway wrote: > That will modify the bytea column so that it is stored uncompressed in > the TOAST table. > > Now, simply use substr() to grab any random chunk: > SELECT substr(foo_bytea, 2, 100) from foo where foo_id = 42; This would imply that every little read wo

Re: [HACKERS] random access - bytea

2003-10-25 Thread Joe Conway
Dennis Bjorklund wrote: There have been (in the past at least) plans on adding a random access interface to bytea fields. I don't find it in the todo, maybe it should be added? First do this: ALTER TABLE foo ALTER COLUMN foo_bytea SET STORAGE EXTERNAL; see: http://www.postgresql.org/docs/view.php?v

[HACKERS] random access - bytea

2003-10-25 Thread Dennis Bjorklund
There have been (in the past at least) plans on adding a random access interface to bytea fields. I don't find it in the todo, maybe it should be added? What kind of syntax have people thought about, to let the client read a bytea field in a random access way? I'm thinking of something like: BEGI