Hi all,
I've a question regarding unique constraints, which I've tried to describe in
general terms, to keep things simple.
I've working on an application that, amongst other things, may add a row to a
table. This table has a primary key defined over two (of the three) fields,
which forces th
On Fri, Apr 15, 2011 at 05:55:07PM +0200, Paul Millar wrote:
>
> ERROR: duplicate key value violates unique constraint [..]
>
> The log files may contain many such messages, depending on the usage-pattern
> of the end-user. Including all these messages in the log file is distracting.
>
On Fri, Apr 15, 2011 at 10:55 AM, Paul Millar wrote:
> Hi all,
>
> I've a question regarding unique constraints, which I've tried to describe in
> general terms, to keep things simple.
>
> I've working on an application that, amongst other things, may add a row to a
> table. This table has a prim
Paul Millar writes:
> Hi all,
>
> I've a question regarding unique constraints, which I've tried to describe in
> general terms, to keep things simple.
>
> I've working on an application that, amongst other things, may add a row to a
> table. This table has a primary key defined over two (of t
On Fri, Apr 15, 2011 at 02:04:49PM -0400, Jerry Sievers wrote:
> set log_min_messages to fatal;
I thought changing the log_min_messages required superuser access?
(That's what the docs say, and what I'd expect too.)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing l
Andrew Sullivan writes:
> On Fri, Apr 15, 2011 at 02:04:49PM -0400, Jerry Sievers wrote:
>
>> set log_min_messages to fatal;
>
> I thought changing the log_min_messages required superuser access?
> (That's what the docs say, and what I'd expect too.)
Oops!... Yup. Forgot about that.
I'll go ea
