From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Bernard <bht(at)actrix(dot)gen(dot)nz> |
Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: BUG #1830: Non-super-user must be able to copy from a |
Date: | 2005-08-19 00:27:01 |
Message-ID: | 43052755.7000003@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
Bernard wrote:
> The majority of JDBC users trying to bulk load tables would not want
> to send the data through their connection. This connection is designed
> to send commands and to transfer only as much data as necessary and as
> little as possible.
I don't understand why this is true at all -- for example, our
application currently does bulk INSERTs over a JDBC connection, and
moving to COPY has been an option I looked at in the past. Importing
lots of data from a remote machine is hardly an uncommon case.
> The need is only created by the limitations of the Postgres COPY
> command.
>
> I can't see why a workaround should be developed instead of or before
> fixing the COPY command.
>
> It works in other DB engines.
I guess that other DB engines don't care about unprivileged DB users
reading any file that the backend can access.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Bernard | 2005-08-19 00:57:04 | Re: BUG #1830: Non-super-user must be able to copy from a |
Previous Message | Bernard | 2005-08-18 23:37:23 | Re: BUG #1830: Non-super-user must be able to copy from a |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-08-19 00:52:17 | Re: total db lockup |
Previous Message | elein | 2005-08-19 00:02:18 | Re: <IDLE> in transaction |