pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedRestricting access to Large objects
5+ messages / 4 participants
[nested] [flat]
* Restricting access to Large objects
@ 2001-10-10 19:23 Aasmund Midttun Godal <aasmund@godal.com>
0 siblings, 0 replies; 5+ messages in thread
From: Aasmund Midttun Godal @ 2001-10-10 19:23 UTC (permalink / raw)
To: pgsql-sql
I can't find any docs / mails on this subject.
How can I restrict access to large objects.
1.) Based on users.
2.) Rules/triggers?
Thanx.
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
^ permalink raw reply [nested|flat] 5+ messages in thread
* Restricting access to Large objects
@ 2001-10-10 20:18 Aasmund Midttun Godal <aasmund@godal.com>
2001-10-16 21:04 ` Re: Restricting access to Large objects Christopher Sawtell <csawtell@paradise.net.nz>
0 siblings, 1 reply; 5+ messages in thread
From: Aasmund Midttun Godal @ 2001-10-10 20:18 UTC (permalink / raw)
To: pgsql-sql
I sent with the wrong email first. sorry.
I can't find any docs / mails on this subject.
How can I restrict access to large objects.
1.) Based on users.
2.) Rules/triggers?
Thanx.
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
---------- End Forwarded Message ----------
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Restricting access to Large objects
2001-10-10 20:18 Restricting access to Large objects Aasmund Midttun Godal <aasmund@godal.com>
@ 2001-10-16 21:04 ` Christopher Sawtell <csawtell@paradise.net.nz>
2001-10-17 03:56 ` Re: Restricting access to Large objects Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Christopher Sawtell @ 2001-10-16 21:04 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Aasmund Midttun Godal <aasmund@godal.com>; +Cc: pgsql-sql
On Tue, 16 Oct 2001 03:46, Tom Lane wrote:
> "Aasmund Midttun Godal" <aasmund@godal.com> writes:
> > How can I restrict access to large objects.
>
> You can't. This is one of the many deficiencies of large objects.
But now that the limit on row length / size has gone away, and that the new
BYTEA type has appeared, it would seem that the need for large objects is
redundant. Someone with more knowledge than I might like to comment.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Restricting access to Large objects
2001-10-10 20:18 Restricting access to Large objects Aasmund Midttun Godal <aasmund@godal.com>
2001-10-16 21:04 ` Re: Restricting access to Large objects Christopher Sawtell <csawtell@paradise.net.nz>
@ 2001-10-17 03:56 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2001-10-17 03:56 UTC (permalink / raw)
To: csawtell@paradise.net.nz; +Cc: Aasmund Midttun Godal <aasmund@godal.com>; pgsql-sql
Christopher Sawtell <csawtell@paradise.net.nz> writes:
> On Tue, 16 Oct 2001 03:46, Tom Lane wrote:
>> You can't. This is one of the many deficiencies of large objects.
> But now that the limit on row length / size has gone away, and that the new
> BYTEA type has appeared, it would seem that the need for large objects is
> redundant. Someone with more knowledge than I might like to comment.
Indeed, large objects are looking rather dinosaurian to me. TOASTed
fields seem a far more natural and flexible way of dealing with large
values.
We still have some work to do on TOASTed fields --- for example, there's
no API to read or write segments of a TOASTed field, as there is for
large objects. And it'd be nice to be able to store or retrieve BYTEA
values without worrying about quoting/escaping problems. But it makes
a lot more sense to expend effort on fixing those issues than it does
to expend effort on improving support for large objects. IMHO anyway.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Restricting access to large objects.
@ 2001-10-10 21:07 Aasmund Midttun Godal <postgresql@envisity.com>
0 siblings, 0 replies; 5+ messages in thread
From: Aasmund Midttun Godal @ 2001-10-10 21:07 UTC (permalink / raw)
To: pgsql-sql
I sent with the wrong email first. sorry.
I can't find any docs / mails on this subject.
How can I restrict access to large objects.
1.) Based on users.
2.) Rules/triggers?
Thanx.
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2001-10-17 03:56 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-10-10 19:23 Restricting access to Large objects Aasmund Midttun Godal <aasmund@godal.com>
2001-10-10 20:18 Restricting access to Large objects Aasmund Midttun Godal <aasmund@godal.com>
2001-10-16 21:04 ` Christopher Sawtell <csawtell@paradise.net.nz>
2001-10-17 03:56 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-10-10 21:07 Restricting access to large objects. Aasmund Midttun Godal <postgresql@envisity.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox