On Sat, 25 Feb 2023 at 19:06, Tom Lane wrote:
> That could be a piece of the puzzle, yeah.
>
>
Thank you very much, this conversion has been a great help.
Regards, Noel Grandin
Noel Grandin writes:
> OK, so it seems like so far my design is not far off the PostgreSQL design
> (which is very comforting).
> I wonder if the difference is in the client<->server protocol.
That could be a piece of the puzzle, yeah.
> Does PostgreSQL hold the transaction open until the clien
On Sat, 25 Feb 2023 at 08:33, Tom Lane wrote:
> Yeah, Postgres has an analogous kind of problem. Our standard way to
> use "large objects" is to store their identifying OIDs in tables,
>
...
> and in particular they can *not* close the transaction that read the
> OID if they'd like to read a ma
Noel Grandin writes:
> On Fri, 24 Feb 2023 at 17:39, Tom Lane wrote:
>> Postgres doesn't really do LOB in the same sense that some other DBs
>> have, so you'd need to specify what you have in mind in Postgres
>> terms to get a useful answer.
> So, specifically, the primary problem we have is thi
Thanks for the answers.
So, H2, like PostgreSQL, also internally has (a) an MVCC engine and (b)
LOBs existing as a on-the-side extra thing.
On Fri, 24 Feb 2023 at 17:39, Tom Lane wrote:
> Postgres doesn't really do LOB in the same sense that some other DBs
> have, so you'd need to specify what
Noel Grandin writes:
> Hacker from another open-source DB here (h2database.com).
> How does postgresql handle the following situation?
> (1) a table containing a LOB column
Postgres doesn't really do LOB in the same sense that some other DBs
have, so you'd need to specify what you have in mind
Hi
Hacker from another open-source DB here (h2database.com).
How does postgresql handle the following situation?
(1) a table containing a LOB column
(2) a query that does
ResultSet rs = query("select lob_column from table_foo");
while (rs.next())
{
retrieve_lob_data(rs.getLob(1));
