agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Andreas Joseph Krogh <andreas@visena.com>
To: pgsql-sql@postgresql.org
Subject: Re: BLOBs
Date: Tue, 12 Jan 2016 08:09:12 +0100 (CET)
Message-ID: <VisenaEmail.28.b34dfb9e97714ef1.15234a51da7@tc7-visena> (raw)
In-Reply-To: <653214003.3602816.1452562366970.JavaMail.yahoo@mail.yahoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
På tirsdag 12. januar 2016 kl. 02:32:46, skrev Eugene Yin <eugeneymail@ymail.com
<mailto:eugeneymail@ymail.com>>:
I did some search on the OID data type. Here is something I found regarding
to the deletion of the OID data.
QUOTE:
"The Large Object method for storing binary data is better suited to storing
very large values, but it has its own limitations. Specifically deleting a row
that contains a Large Object reference does not delete the Large Object.
Deleting the Large Object is a separate operation that needs to be performed.
Large Objects also have some security issues since anyone connected to the
database can view and/or modify any Large Object, even if they don't have
permissions to view/update the row containing the Large Object reference."
F <mailto:pgsql-sql@postgresql.org>rom:
https://jdbc.postgresql.org/documentation/84/binary-data.html
<https://jdbc.postgresql.org/documentation/84/binary-data.html;
So I have two questions:
1) If it is true that "Deleting the Large Object is a separate operation that
needs to be performed.", after the deletion, what operation I need to perform,
in order to delete the OID data in the table? Possiblely put into an after
trigger
2) "Large Objects also have some security issues since anyone connected to the
database can view and/or modify any Large Object". Will this pose a real risk
to the security? or just a forethought?
1) You don't need to perform any "after delete"-operation as a developer. But
the DBA (or someone else) has to execute vacuumlo (see "man vacuumlo" for more
info) using cron or some other periodic scheduling tool.
2) Your mileage may vary, but for our app this isn't an issue.
PS: 8.4 is EOL, use a more current version, preferably 9.5.
I also recommend the -ng driver as it's the only one with proper BLOB-support,
as mentioned earlier in this thread.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas@visena.com <mailto:andreas@visena.com>
www.visena.com <https://www.visena.com;
<https://www.visena.com;
view thread (20+ messages) latest in thread
Message-ID: <VisenaEmail.28.b34dfb9e97714ef1.15234a51da7@tc7-visena>
Permalink: ../VisenaEmail.28.b34dfb9e97714ef1.15234a51da7@tc7-visena/
Also on: postgresql.org/message-id/VisenaEmail.28.b34dfb9e97714ef1.15234a51da7@tc7-visena
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: andreas@visena.com
Subject: Re: BLOBs
In-Reply-To: <VisenaEmail.28.b34dfb9e97714ef1.15234a51da7@tc7-visena>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox