Hi All,
(B
(BI have a v7.1 database whose encoding is EUC_JP and I'm trying to get it
(Binto a v7.4 database whose encoding is also EUC_JP. Unfortunately it seems
(Bthat 7.4 is much stricter about it's multibyte data then 7.1 was because
(Battempts to restore into the 7.4 db result in "Inva
Dear Gurus,
Please show me to the right manual/discussion if my questions are already
answered/solved.
1. DEBUG message level separation:
In v7.3 there were the annoying DEBUG messages Start/CloseTransactCommand.
In v7.4 you could eliminate them from user DEBUG messages by logging from
DE
I must be blind... I can't find the part in the manuals that tells me
how to set the search_path in JDBC. Can someone please nudge me in the
right direction?
I did RTFM before posting!
Thanks,
Brad
---(end of broadcast)---
TIP 8: explain analyze is
I've seen book that prefer installing PostgreSQL as root and another one
recommends otherwise by first creating a postgres account and then
installing it as postgres. In the Oracle world, you don't use root to
install the software. What is the best practice as far as PostgreSQL
goes?
--
Husam
*
Tomeh, Husam wrote:
I've seen book that prefer installing PostgreSQL as root and another one
recommends otherwise by first creating a postgres account and then
installing it as postgres. In the Oracle world, you don't use root to
install the software. What is the best practice as far as PostgreS
On Wed, 12 Jan 2005 15:30:06 -0800, Tomeh, Husam <[EMAIL PROTECTED]> wrote:
> I've seen book that prefer installing PostgreSQL as root and another one
> recommends otherwise by first creating a postgres account and then
> installing it as postgres. In the Oracle world, you don't use root to
> insta
Tomeh, Husam wrote:
> I've seen book that prefer installing PostgreSQL as root and another
> one recommends otherwise by first creating a postgres account and
> then installing it as postgres. In the Oracle world, you don't use
> root to install the software. What is the best practice as far as
> P
On Thu, 13 Jan 2005 01:00:31 +0100, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Tomeh, Husam wrote:
> > I've seen book that prefer installing PostgreSQL as root and another
> > one recommends otherwise by first creating a postgres account and
> > then installing it as postgres. In the Oracle worl
Peter Eisentraut wrote:
Tomeh, Husam wrote:
I've seen book that prefer installing PostgreSQL as root and another
one recommends otherwise by first creating a postgres account and
then installing it as postgres. In the Oracle world, you don't use
root to install the software. What is the best practi
On January 12, 2005 04:31 pm, Joshua D. Drake wrote:
> Peter Eisentraut wrote:
> > Tomeh, Husam wrote:
> >>I've seen book that prefer installing PostgreSQL as root and another
> >>one recommends otherwise by first creating a postgres account and
> >>then installing it as postgres. In the Oracle wor
The current recommendation, which is reflected in the installation
instructions, is to install the software as root and to use the
postgres user for the database files. The advice seen elsewhere in
this thread to use the postgres user also for the software files is
wrong.
As a security profe
Darcy Buskermolen wrote:
On January 12, 2005 04:31 pm, Joshua D. Drake wrote:
Peter Eisentraut wrote:
Tomeh, Husam wrote:
I've seen book that prefer installing PostgreSQL as root and another
one recommends otherwise by first creating a postgres account and
then installing it as postg
Christopher Petrilli <[EMAIL PROTECTED]> writes:
> On Thu, 13 Jan 2005 01:00:31 +0100, Peter Eisentraut <[EMAIL PROTECTED]>
> wrote:
>> The current recommendation, which is reflected in the installation
>> instructions, is to install the software as root and to use the
>> postgres user for the dat
Peter,
You may well be on the development team, but you are wrong for
one very important reason. If the Postgresql executables are owned by
root they execute with the priviledges of root. Thereby any local
created extensions like database_size also execute with the priviledges
of root.
Peter,
You may well be on the development team, but you are wrong for
one very important reason. If the Postgresql executables are owned by
root they execute with the priviledges of root. Thereby any local
created extensions like database_size also execute with the priviledges
of root.
On Wed, 12 Jan 2005, Goulet, Dick wrote:
> You may well be on the development team, but you are wrong for
> one very important reason. If the Postgresql executables are owned by
> root they execute with the priviledges of root. Thereby any local
Not on any reasonable system unless instal
Whatever, I'll keep root only for absolutely restricted use & install
under a separate user account. Works just fine & it makes the auditors
& sysadmin feel better.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-Original Message-
From: Stephan Szabo [mailto:[EMAIL PROTECTED]
Se
Goulet, Dick wrote:
> Peter,
>
> You may well be on the development team, but you are wrong for
> one very important reason. If the Postgresql executables are owned by
> root they execute with the priviledges of root. Thereby any local
What? They are not setuid?
--
On Wed, 12 Jan 2005, Goulet, Dick wrote:
> Whatever, I'll keep root only for absolutely restricted use & install
> under a separate user account. Works just fine & it makes the auditors
> & sysadmin feel better.
Unfortunately, I _know_ how auditors think, but I would hope that a
sensible compan
Goulet, Dick wrote:
Whatever, I'll keep root only for absolutely restricted use & install
under a separate user account. Works just fine & it makes the auditors
& sysadmin feel better.
I don't argue the point of using root. I agree with you there.
Just the point that if it is owned by root it
Christopher Petrilli <[EMAIL PROTECTED]> writes:
> As a security professional, why would the root user need to be
> involved in the ownership of PostgreSQL? I see no reason for this,
> but perhaps I'm missing something important.
A number of years ago some Unices experimented with installing sys
21 matches
Mail list logo
