From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>, Petr Jelinek <pjmodos(at)pjmodos(dot)net> |
Subject: | Re: GRANT ON ALL IN schema |
Date: | 2009-08-10 07:42:34 |
Message-ID: | 200908101042.35024.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wednesday 05 August 2009 19:59:52 Tom Lane wrote:
> Or maybe we are going at this the wrong way? Would it be better to try
> harder to support the write-a-plpgsql-function approach?
This would become much simpler if you could just execute plpgsql code instead
of having to define a function around it. And perhaps if the plpgsql parser
where a bit smarter.
Example:
RUN LANGUAGE plpgsql $$
FOR schema_name, table_name FROM information_schema.tables WHERE whatever LOOP
GRANT ALL ON TABLE schema_name.table_name TO someuser;
END LOOP $$;
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2009-08-10 07:45:34 | CommitFest reviews and application support |
Previous Message | Peter Eisentraut | 2009-08-10 07:24:31 | Re: [COMMITTERS] pgsql: Ship documentation without intermediate tarballs Documentation |