2012/1/8 Thomas Kellerer <spam_eater@xxxxxxx>:> What's the reason for you to stick with LargeObjects? I simply used the @Lob annotation in Hibernate/JPA. That's all to get a leaking pg_largeobject table. See http://relation.to/Bloggers/PostgreSQLAndBLOBs, https://hibernate.onjira.com/browse/HHH-2244 and https://hibernate.onjira.com/browse/HHH-4876 for some background of the dilemma. Stefan 2012/1/8 Thomas Kellerer <spam_eater@xxxxxxx>: > Stefan Keller wrote on 08.01.2012 19:13: > >>> I think you are better off using bytea unless you need to access only >>> parts the blob regularly. >> >> >> That's a valid tip. But it's to the current JDBC implementation to >> take action because it currently leads to disk space leakage when >> using JDBC and JPA/Hibernate. > > > But only if you use large objects. > > From my perspective bytea is the (only) data type that matches the JDBC BLOB > type. > And none of the problems you have occur when using bytea. > > There is no match for PG's large objects in the JDBC API so I don't see your > claim that it's a fault of the driver. > > What's the reason for you to stick with LargeObjects? > > > > > > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
