Ð ÐÑÑ, 13.07.2004, Ð 04:43, mike g ÐÐÑÐÑ:
> Hello,
>
> It is possible to enable the statements issued against the db to be
> logged in postgresql.conf(log_statement = true). Depending on the OS
> then you can filter the logs or maybe create a Perl script to scan the
> logs.
Does that help when f
Hi all,
why don't you create comp.database.postgresql.slony NG ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
> Keeping the system administrator from seeing the data while making it
> searchable is difficult. To do this you need to encrypt the data on
> the client side using a key the client has (and this key has to be
> protected from loss) and the only searches you can do are equality
> searches using a
On Mon, 2004-07-12 at 10:26, Konstantin Pelepelin wrote:
> The
> > > best solution I see is having an (per session)
> > > idle_transaction_timeout or idle_connection_timeout
> > > setting. But there is no such thing in postgres!
> > > Scanning through list I've not found any workaround.
Have you
I found that it was actually a '\\N' value only that causes
dumps to dump successfully, but fail on import (When using COPY),
because both '\N' and '\\N' are seen as null by the COPY statement.
I just happened to have '\\N' values in my NOT NULL text field.
I now manually use this dump command :
p
On Tue, Jul 13, 2004 at 09:54:29 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> Hi all,
> why don't you create comp.database.postgresql.slony NG ?
It isn't that simple. For big 8 newsgroups you have to make a proposal
and people vote on it. You need 100 more Yes's than No's.
-
On Tue, Jul 13, 2004 at 11:35:57 +0200,
Daniel Struck <[EMAIL PROTECTED]> wrote:
> > Keeping the system administrator from seeing the data while making it
> > searchable is difficult. To do this you need to encrypt the data on
> > the client side using a key the client has (and this key has to be
> If you decrypt the data on the database, the sysadmin can see it.
Hm, you are right. If one does decrypt the data on the database you have to sent the
password to postgresql and so a administrator of the database could easily grasb the
password.
So the only way to go, would be to perform en/d
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>
> On Tue, Jul 13, 2004 at 09:54:29 +0200,
> Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> > Hi all,
> > why don't you create comp.database.postgresql.slony NG ?
>
> It isn't that simple. For big 8 newsgroups you have to make a proposal
> and people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Wolff III wrote:
| On Tue, Jul 13, 2004 at 09:54:29 +0200,
| Gaetano Mendola <[EMAIL PROTECTED]> wrote:
|
|>Hi all,
|>why don't you create comp.database.postgresql.slony NG ?
|
|
| It isn't that simple. For big 8 newsgroups you have to make a p
On Tue, Jul 13, 2004 at 15:32:49 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruno Wolff III wrote:
>
> | On Tue, Jul 13, 2004 at 09:54:29 +0200,
> | Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> |
> |>Hi all,
> |>why don't you create
Daniel Struck wrote:
If you decrypt the data on the database, the sysadmin can see it.
Hm, you are right. If one does decrypt the data on the database you have to sent
the password to postgresql and so a administrator of the database could easily grasb
the password.
So the only way to go, wo
Stef <[EMAIL PROTECTED]> writes:
> I found that it was actually a '\\N' value only that causes
> dumps to dump successfully, but fail on import (When using COPY),
> because both '\N' and '\\N' are seen as null by the COPY statement.
This is demonstrably not so. You might have trouble with data co
Tom Lane mentioned :
=> This is demonstrably not so. You might have trouble with data coming
=> from somewhere else, if the source doesn't understand the quoting rules
=> for COPY data. But I can dump and restore a table containing '\N' and
=> variants of that without any trouble.
Here's what I
Stef <[EMAIL PROTECTED]> writes:
> Here's what I did to recreate the problem :
> ...
> Welcome to psql 7.3.4, the PostgreSQL interactive terminal.
Ah. I was checking it in 7.4. I thought we'd fixed this issue further
back than 7.4, but some digging in the CVS logs shows not:
2003-10-05 22:38 t
On Tue, 13 Jul 2004 11:31:37 +0100, Simon Riggs <[EMAIL PROTECTED]>
wrote:
> > best solution I see is having an (per session)
> > idle_transaction_timeout or idle_connection_timeout
> > setting. But there is no such thing in postgres!
Have you looked at statement_timeout?
This doesn't do exactl
Hi,
I built my Solaris PostgreSQL 7.4.2 installation
using:
configure --disable-shared
My reason was so that clients that install it would
have everything there in one binary tar file and would
not have to install any gcc lib patches, etc.
Anyway, everything seemed to work great until I wante
PITR Patch v5_1 just posted has Point in Time Recovery working
Still some rough edgesbut we really need some testers now to give
this a try and let me know what you think.
Klaus Naumann and Mark Wong are the only [non-committers] to have tried
to run the code (and let me know about it), s
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
>
[snip]
>
> I was believing that the NGs news.XX.postgresql.org were managed by
> postgresql developer group and the vote could be easily done trough a
> poll in the postgresql web site.
For postgresql.org's own news servers, maybe. I really don't kno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Wolff III wrote:
| On Tue, Jul 13, 2004 at 15:32:49 +0200,
| Gaetano Mendola <[EMAIL PROTECTED]> wrote:
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>Bruno Wolff III wrote:
|>
|>| On Tue, Jul 13, 2004 at 09:54:29 +0200,
|>| Gaetano
I believe you are correct. I will check my logs later. If you have access to the
code you could add individual sequences within each procedures and use those as
counters.
On Tue, Jul 13, 2004 at 10:07:33AM +0200, Markus Bertheau wrote:
> Ð ÐÑÑ, 13.07.2004, Ð 04:43, mike g ÐÐÑÐÑ:
> > Hello,
> >
Ð ÐÑÐ, 14.07.2004, Ð 03:35, Mike G ÐÐÑÐÑ:
> I believe you are correct. I will check my logs later. If you have
> access to the code you could add individual sequences within each
> procedures and use those as counters.
This is a very odd and costly way, which is why I asked if the
statistics col
Can you give us some suggestions of what kind of stuff to test? Is
there a way we can artificially kill the backend in all sorts of nasty
spots to see if recovery works? Does kill -9 simulate a 'power off'?
Chris
Simon Riggs wrote:
PITR Patch v5_1 just posted has Point in Time Recovery working
AFAIK nothing along those lines is planned. I have been reading lists
for a few months and nothing in the TODO currently. 7.5 will have more
detail in the logs but probably not what you are looking for.
You can plead your case in the hacker mailing list and perhaps they will
add it to the todo l
[EMAIL PROTECTED] (Jim Seymour) writes:
> http://www.faqs.org/faqs/usenet/creating-newsgroups/part1/ will give
> you an idea of the process.
AFAIK *none* of the comp.databases.postgresql newsgroups have actually
been put through the vote process, and so they are all rogue groups in
the eyes of peo
25 matches
Mail list logo
