bkim <[EMAIL PROTECTED]> writes:
> Is it possible to use a dedicated log file for each database?
Sure, if you run a separate postmaster for each database.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked ou
"Dario Ottaviano" <[EMAIL PROTECTED]> writes:
> So, for istance, if i write the date: 04/03/2004 (4 Mar 2004), it writes the
> date 03/04/2004 (3 Apr 2004) into the table .
You need to change the DateStyle setting to agree with your desired
format.
regards, tom lane
-
* Elielson Fontanezi <[EMAIL PROTECTED]> [2004-03-02 15:47:13 -0300]:
Hi,
>I am in the need of using some multi-master replication for
>postgres.
I've implemented something in php. All my applications do their database
access layer, where they only touch whole objects (the structure
Hi Bruce and admin list
users!
I am
in the need of using some multi-master replication for
postgres.
I´ve
been searching the internet two days so far and I can´t find
anything about it rather
than Postgres-R, pgReplication and so on.
All projects I saw use
master-slave techniqu
Hi!
I came to ur e-mail address from one of the sites through google. Hope u
could help me please.
I am using red hat linux and running my perl programs with postgresql at
back end.
The follwing error occurs while using Pg.
Can't locate Pg.pm in @INC
Hi there...
I write it becouse i need to know where can i get a "SPECIFIC DOCUMENT" with
the "Postgresql Administration Functions" like
- Create User
- Create Group
...
...
..
.
etc.
I just need a Document which explains very shortly every function(as
administrator).
Thanks fo
Hi:
I have a PostgreSQL 7.2.2 running in a Linux Mandrake 8.2 Server.
I want to upgrade to PostgreSQL 7.3
I would like to accomplish this by installing fit rpm packages, because my
linux skills are limited.
However, there aren't any packages of PostgreSQL 7.3 for Mandrake 8.2
I must be careful be
Dear list,
Is it possible to use a dedicated log file for each database? I think
it's possible in other database servers, but couldn't find the same from
postgresql documents or web search.
Regards,
Ben
---(end of broadcast)---
TIP 4: Don't 'kill
Hi, i use Postgresql 7.2 on a windows server (Win 2000 Server).
The problem is that when i write a date into a timestamp field of a table,
it writes it in to No-Europe format.
So, for istance, if i write the date: 04/03/2004 (4 Mar 2004), it writes the
date 03/04/2004 (3 Apr 2004) into the table .
> BTW: if you have a USA-based company and collect info regarding Italian
> people, you have to comply with this absurd Italian law. Funny, isn't it?
No, we don't. We're not bound by Italian law, only US law.
Michael
--
Michael Darrin Chaney
[EMAIL PROTECTED]
http://www.michaelchaney.com/
---
Hi all,
I am wondering how you guys back up your databases. Say, I have a 20 GB
database, data and indexes. If I run pg_dump on this, it backs up the schema
and the data. When I have to restore this, I whould have to run this through
psql which would then re-build the indexes after it has inser
On Fri, Mar 05, 2004 at 20:12:37 +,
Silvana Di Martino <[EMAIL PROTECTED]> wrote:
>
> BTW: if you have a USA-based company and collect info regarding Italian
> people, you have to comply with this absurd Italian law. Funny, isn't it?
Only if you are going to come within reach of Italian LE
On Fri, 5 Mar 2004, Silvana Di Martino wrote:
> Alle 19:38, venerdì 5 marzo 2004, scott.marlowe ha scritto:
> > > Unfortunately, the new Italian law forces us to take seriously into
> > > account this catastrophic scenario and another one that is almost as
> > > worring: an unfaithful SysAdmin tha
On Fri, 5 Mar 2004, Silvana Di Martino wrote:
> Alle 20:14, venerdì 5 marzo 2004, Stephan Szabo ha scritto:
> > > Unfortunately, the new Italian law forces us to take seriously into
> > > account this catastrophic scenario and another one that is almost as
> > > worring: an unfaithful SysAdmin tha
Alle 20:14, venerdì 5 marzo 2004, Stephan Szabo ha scritto:
> > Unfortunately, the new Italian law forces us to take seriously into
> > account this catastrophic scenario and another one that is almost as
> > worring: an unfaithful SysAdmin that copies your data and sells them to
> > KGB. So, datab
Alle 19:38, venerdì 5 marzo 2004, scott.marlowe ha scritto:
> > Unfortunately, the new Italian law forces us to take seriously into
> > account this catastrophic scenario and another one that is almost as
> > worring: an unfaithful SysAdmin that copies your data and sells them to
> > KGB. So, datab
Alle 19:26, venerdì 5 marzo 2004, Hans Spaans ha scritto:
> I'm just wondering, does that law applies on all databases or just on
> new databases. In the Netherlands laws about privacy only apply on new
> databases and for old databases the law of that time-frame only
> applies. I must note that th
On Fri, 5 Mar 2004, Silvana Di Martino wrote:
> Alle 15:11, venerdì 5 marzo 2004, Alex Page ha scritto:
> > If you're trying to protect against somebody taking down your server
> > room door with a sledgehammer, lifting your server out of the rack,
> > driving it away and booting off an alternativ
Alle 13:53, venerdì 5 marzo 2004, Mark Gibson ha scritto:
> Silvana Di Martino wrote:
> >Is there any (native/third party) tool for encrypting a PGSQL database on
> > the disk? Is there any PGSQL option for encrypting data on the fly?
>
> Have a look in contrib/pgcrypto.
> Although I haven't actual
On Fri, 5 Mar 2004, Silvana Di Martino wrote:
> Alle 15:11, venerdì 5 marzo 2004, Alex Page ha scritto:
> > If you're trying to protect against somebody taking down your server
> > room door with a sledgehammer, lifting your server out of the rack,
> > driving it away and booting off an alternativ
Alle 15:00, venerdì 5 marzo 2004, Mitch Pirtle ha scritto:
> My question is much more basic than that: Why encrypt anything beyond
> passwords? If you secure the accounts on the machine, and encrypt all
> network traffic to the machine (ssh, scp, ssl) then what additional
> security can you add?
Alle 11:17, venerdì 5 marzo 2004, Matt Clark ha scritto:
> Yes, but only if the password has to entered manually [1] at boot time.
> And it gives zero protection against someone who gains root access to the
> server.
This is a problem for italian users because the italian law clearly states
that
Alle 12:12, venerdì 5 marzo 2004, Dave Ewart ha scritto:
> If you find any 'automated' front-end to do this at the database-level,
> rather than something like loopback at the filesystem level or at the
> field level for specific fields, I think there would be a lot of
> interest.
As I told in ano
Alle 13:53, venerdì 5 marzo 2004, Mitch Pirtle ha scritto:
> The same logic applies to encrypting the data in the database -
> somewhere on your server the application has to know how to decrypt it,
> and that means anyone that gains access to your server will have that
> ability also...
That's tr
Alle 15:11, venerdì 5 marzo 2004, Alex Page ha scritto:
> If you're trying to protect against somebody taking down your server
> room door with a sledgehammer, lifting your server out of the rack,
> driving it away and booting off an alternative medium to avoid needing
> to know your root password,
Alle 11:30, venerdì 5 marzo 2004, Radu-Adrian Popescu ha scritto:
> We're basically doing it this way: generate a pair of private/public
> keys and save these.
> Then we get sensitive data in from some outside source, use it in the
> processing part,
> then we encrypt it using the public key (obvio
On Fri, Mar 05, 2004 at 12:52:05PM +, Silvana Di Martino wrote:
> At the moment, our data are on a server protected by a firewall and accessible
> just by authorized people. This was clearly declared as being "sufficient" by
> the italian law until December 2003. The new law, instead, clear
On Friday 05 March 2004 10:31, Mitch Pirtle wrote:
[snip]
> 1) I've never seen a quad-xeon live on a UPS for more than 90 seconds
I had mine (Acer Altos G900) running for more than 10 minutes the other day,
until I decied the outage would take a little longer than usual and shut
everything dow
On Fri, Mar 05, 2004 at 10:00:23 -0500,
Mitch Pirtle <[EMAIL PROTECTED]> wrote:
>
> Second, hard-disk encryption will only come into play if someone stole
> the hardware, right? And even then, as long as the thing boots, then
> they would have access! That is, unless we went back to the
> h
On Fri, Mar 05, 2004 at 10:31:41 -0500,
Mitch Pirtle <[EMAIL PROTECTED]> wrote:
>
> 1) I've never seen a quad-xeon live on a UPS for more than 90 seconds
A UPS isn't supposed to do that. Its purpose to is to allow for a clean
shutdown or time to switch to an alternate power source. You need a b
On Fri, Mar 05, 2004 at 07:43:10 -0700,
Matt Davies <[EMAIL PROTECTED]> wrote:
> And how does one account for key information? If one encrypts any information
> deemed worthy to be a key then you have to decrypt the entire database to find
> particular information.
It depends on what kinds of
Matt Davies wrote:
And how does one account for key information? If one encrypts any information
deemed worthy to be a key then you have to decrypt the entire database to find
particular information.
Of course, you could keep keys unencrypted for use, but then again, why encrypt
it at all?
My q
Quoting Mitch Pirtle <[EMAIL PROTECTED]>:
> Matt Davies wrote:
>
> > And how does one account for key information? If one encrypts any
> information
> > deemed worthy to be a key then you have to decrypt the entire database to
> find
> > particular information.
> >
> >
> > Of course, you coul
On Fri, Mar 05, 2004 at 08:53:04AM -0500, Mitch Pirtle wrote:
> I understand (and demand) requiring SSL connections for database
> clients, and MD5 hashing of passwords before storing in the database,
> but implementing two-way encryption of database data just doesn't make
> sense to me.
It al
Alex Page wrote:
It all comes down to what you're trying to protect your data *from*. If
you're trying to protect it from people sniffing network traffic between
clients and the server, then SSL is sensible. If you're trying to
protect against somebody reading passwords out of a database and using
Mark Gibson wrote:
Are there any Gentoo users here?
Do you wish the PostgreSQL ebuild made use of SLOTS?
I've submitted a slotted ebuild for testing at:
http://bugs.gentoo.org/show_bug.cgi?id=42894
It's the first slotted ebuild i've attempted, so it may be total rubish!
But I have managed to get 7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
the followin link on all mirrors is empty.
ftp://ftp.at.postgresql.org/db/www.postgresql.org/pub/binary/v7.4.1/redhat/rhas-2.1/
Any way to recompile the SRPMS for rhas2.1 ?
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuP
And how does one account for key information? If one encrypts any information
deemed worthy to be a key then you have to decrypt the entire database to find
particular information.
Of course, you could keep keys unencrypted for use, but then again, why encrypt
it at all?
Quoting Mitch Pirtl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, 05.03.2004 at 14:47 +0100, Grega Bremec wrote:
> > > [1] There are ways of avoiding having to enter the info manually,
> > > but they're very tricky to implement securely.
> >
> > Not sure I follow this - there's no point AT ALL in using L
Dave Ewart wrote:
If you find any 'automated' front-end to do this at the database-level,
rather than something like loopback at the filesystem level or at the
field level for specific fields, I think there would be a lot of
interest.
But that is the problem, isn't it? Any 'automated'
encryption
...and on Fri, Mar 05, 2004 at 12:08:02PM +, Dave Ewart used the keyboard:
> >
> > [1] There are ways of avoiding having to enter the info manually, but
> > they're very tricky to implement securely.
>
> Not sure I follow this - there's no point AT ALL in using LoopAES if you
> can mount the e
On Friday, 05.03.2004 at 12:52 +, Silvana Di Martino wrote:
> Deciding which data are relevant is not easy. The law stipulates that all of
> the "personal data" have to be encrypted and that "personal data" are the
> data that allow a "spy" to infer any of the following information about a
On Friday, 05.03.2004 at 12:51 +, Silvana Di Martino wrote:
> Alle 09:51, venerdì 5 marzo 2004, Dave Ewart ha scritto:
> > I guess there may similar legislation in Italy and elsewhere.
>
> Actually, the Italian law is an implementation of a EU directive
> strictly inspired to the existing UK
On Friday, 05.03.2004 at 11:17 +, Matt Clark wrote:
> > What's wrong with using a LoopAES filesystem? It protects against
> > someone walking off with the server, or at least the hard disk, and
> > being able to see the data.
>
> Yes, but only if the password has to entered manually [1] at b
Alle 09:10, venerdì 5 marzo 2004, Radu-Adrian Popescu ha scritto:
> Are you sure you need to encrypt the _database_ ? It seems strange to
> require encryption
> of all the data, as you would get using LoopAES. I think you only need
> to decide (and probably
> the privacy protection law stipulates t
Alle 09:20, venerdì 5 marzo 2004, Dave Ewart ha scritto:
> What's wrong with using a LoopAES filesystem? It protects against
> someone walking off with the server, or at least the hard disk, and
> being able to see the data.
Nothing! I just wonder if there is any other tool, more specific to
Pos
> What's wrong with using a LoopAES filesystem? It protects against
> someone walking off with the server, or at least the hard disk, and
> being able to see the data.
Yes, but only if the password has to entered manually [1] at boot time.
And it gives zero protection against someone who gains ro
On Friday, 05.03.2004 at 09:21 +, [EMAIL PROTECTED] wrote:
> Is it enough to encrypt some table fields only, i.e. "personnal data"
> personal(social security) number, name-surname and birth data - if one
> can not easily tell whom the data(e.g. bank account) belongs to then
> it may be quite e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, 05.03.2004 at 11:10 +0200, Radu-Adrian Popescu wrote:
> | While I can see how to protect a PGSQL connection using SSH
> | tunneling or a VPN, I cannot see any way to encrypt a PGSQL
> | database stored on a hard disk, put aside the possibil
Is it enough to encrypt some table fields only, i.e. "personnal data"
personal(social security) number, name-surname and birth data - if one can
not easily tell whom the data(e.g. bank account) belongs to then it may be
quite enough?
Just because "personal" data is quite a loose term: it can be al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Silvana Di Martino wrote:
| The new italian law about personal data protection (aka "privacy")
| requires the use of cryptography _both_ for protecting the network
| traffic _and_ for protecting the (personal) data stored on the hard
| disk.
|
| While
The new italian law about personal data protection (aka "privacy") requires
the use of cryptography _both_ for protecting the network traffic _and_ for
protecting the (personal) data stored on the hard disk.
While I can see how to protect a PGSQL connection using SSH tunneling or a
VPN, I cann
52 matches
Mail list logo
