Bruce Momjian writes:
> What to do about exposing the list of possible SQLSTATE error codes
I say we put the list in the documentatio and that's it. Exposing the
list in C header files wouldn't really be an ultimate solution, because
not everyone uses C.
> Freeze message strings
That is old ne
On Mon, Oct 13, 2003 at 11:51:52PM -0400, Jan Wieck wrote:
> You can build more secure systems as long as you want, evolution will
> develop the better idiot. As long as you create safer cars with more
Sure, but I think all Rod is asking for is something like the ability
to add the -w switch to
> >> Some dumb-user/fat-finger/ooops protection is surely welcome, but there
> >> is a limit. A system console has to be behind a locked door instead of
> >> the single-user boot being root-password protected. As soon as people
> >
> > Unfortunately, as more and more companies start to outsourc
Rod Taylor wrote:
On Mon, 2003-10-13 at 21:26, Jan Wieck wrote:
Why do people wait until the EMT cannot give the life-saving infusion
any more before they realize that "invincible" isn't that great at all?
Some dumb-user/fat-finger/ooops protection is surely welcome, but there
is a limit. A sys
On Mon, 2003-10-13 at 21:26, Jan Wieck wrote:
> Rod Taylor wrote:
> >> >> > Allow superuser (dba?) the ability to turn off foreign key checks/all
> >> >> > constraints/triggers, not settable from postgresql.conf?
> >> >>
> >> >> Is that one really necessary for 7.4 now that adding foreign keys i
Rod Taylor wrote:
>> > Allow superuser (dba?) the ability to turn off foreign key checks/all
>> > constraints/triggers, not settable from postgresql.conf?
>>
>> Is that one really necessary for 7.4 now that adding foreign keys is
>> apparently much faster?
If you reconfigure your systems to fo
Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I vote to disable the checks for pg_restore if the dumpfile has a check
> > added to ensure it's the same file that was dumped (an MD5 in the
> > header) and it is a full database restore.
> > Individual table restores should require the
Rod Taylor <[EMAIL PROTECTED]> writes:
> I vote to disable the checks for pg_restore if the dumpfile has a check
> added to ensure it's the same file that was dumped (an MD5 in the
> header) and it is a full database restore.
> Individual table restores should require the check.
It is not our busi
> >> > Allow superuser (dba?) the ability to turn off foreign key checks/all
> >> > constraints/triggers, not settable from postgresql.conf?
> >>
> >> Is that one really necessary for 7.4 now that adding foreign keys is
> >> apparently much faster?
> If you reconfigure your systems to force fs
Bruce Momjian wrote:
Christopher Kings-Lynne wrote:
> Changes
> ---
> Allow superuser (dba?) the ability to turn off foreign key checks/all
> constraints/triggers, not settable from postgresql.conf?
Is that one really necessary for 7.4 now that adding foreign keys is
apparently much faster?
Christopher Kings-Lynne wrote:
>
> > Changes
> > ---
> > Allow superuser (dba?) the ability to turn off foreign key checks/all
> > constraints/triggers, not settable from postgresql.conf?
>
> Is that one really necessary for 7.4 now that adding foreign keys is
> apparently much faster?
Th
Changes
---
Allow superuser (dba?) the ability to turn off foreign key checks/all
constraints/triggers, not settable from postgresql.conf?
Is that one really necessary for 7.4 now that adding foreign keys is
apparently much faster?
Chris
---(end of broadcast)
We only have a few open items left. Let's make final decisions on these
and schedule RC1.
---
P O S T G R E S Q L
7 . 4 O P E NI T E M S
Current at ftp://momj
13 matches
Mail list logo
