From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] COPY .. COMPRESSED |
Date: | 2013-01-15 20:37:07 |
Message-ID: | CAFNqd5WPPyq0u2oOwOiyA6=ttCD29Yyz5hSanTHMP1EqAHy+Ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 15, 2013 at 2:53 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> The popen patch doesn't support the '|compression-binary' option through
> the FE protocol. Even if it did, it would only be available for
> superusers as we can't allow regular users to run arbitrary commands on
> the server-side.
That points towards a fix that involves having a set of non-arbitrary commands
that we allow plain users to use.
Hmm. There's an interesting thought...
How about having a "pg_filters" table in pg_catalog which allows capturing
labels and names of known-to-be-safe binary filters:
insert into pg_filters (label, location)
values
('zcat', '/usr/bin/zcat'),
('bzip2', '/usr/bin/bzip2'),
('bunzip2', '/usr/bin/bunzip2');
And then having some capability to grant permissions to roles to use
these filters.
That's not a "version 1" capability... Suppose we have, in 9.3, that there are
direct references to "|/usr/bin/zcat" (and such), and then hope, in
9.4, to tease
this out to be a non-superuser-capable facility via the above pg_filters?
These filters should be useful for FDWs as well as for COPY.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-01-15 20:40:02 | Re: erroneous restore into pg_catalog schema |
Previous Message | Kohei KaiGai | 2013-01-15 20:28:23 | [sepgsql 2/3] Add db_schema:search permission checks |