[GENERAL] Invitation to connect on LinkedIn

2009-09-13 Thread raghu ram
LinkedIn I'd like to add you to my professional network on LinkedIn. - raghu Accept raghu ram's invite: https://www.linkedin.com/e/isd/734105299/D0TiGEdR/ -- (c) 2009, LinkedIn Corporation

[GENERAL] postgresql.key secure storage

2009-09-13 Thread Saleem EDAH-TALLY
Hello, This concerns use of postgresql.key private key file on the client side. psql can't establish a connection. with an encrypted postgresql.key file. If I'm wrong here, the following is invalid and please show me the steps I'm ignoring. An application using libpq would require that the pri

[GENERAL] How to match sets?

2009-09-13 Thread Alban Hertroys
Greetings! I'm having some troubles creating a query, or rather, I can write one that works but the approach feels wrong! The problem at hand boils down to finding a record in a group where each result of two result- sets matches on some columns. The actual data I need to match isn't direc

Re: [GENERAL] postgresql.key secure storage

2009-09-13 Thread Adam Tauno Williams
> An application using libpq would require that the private unencrypted key be > deployed to the end user, together with the public key and trust cert. This > would mean if the end user is curious enough and computer litterate, he can > bypass the client application and make a direct connection

Re: [GENERAL] postgresql.key secure storage

2009-09-13 Thread Saleem EDAH-TALLY
>A user must have the TRUNCATE privilege to truncate a table or be the >tables owner. Well the TRUNCATE example I mentioned is perhaps not explicit of what I meant to say. A user who can modify data in a client application can also modify data if he connects directly to the database, bypassing t

Re: [GENERAL] postgresql.key secure storage

2009-09-13 Thread Adam Tauno Williams
> An application using libpq would require that the private unencrypted key be > deployed to the end user, together with the public key and trust cert. This > would mean if the end user is curious enough and computer litterate, he can > bypass the client application and make a direct connection

[GENERAL] schema proxying virtual database

2009-09-13 Thread Rajesh Kumar Mallah
Dear List, There are many opensource applications that support postgresql (eg , gforge , bricolage , dspam ..) but does not use schemas(namespaces) as a result of which you are forced to use/create a new database and loose the advantage of linking the application data with your existing database.

Re: [GENERAL] schema proxying virtual database

2009-09-13 Thread Dimitri Fontaine
Rajesh Kumar Mallah writes: > my question is , is it a feasible idea to have some special kind of database > in the postgresql cluster that mimics a schema of an existsing > database. Try abusing pgbouncer to this effect. Configure several pgbouncer databases pointing to the same physical one, w

Re: [GENERAL] How to match sets?

2009-09-13 Thread Harald Fuchs
In article , Alban Hertroys writes: > An example of the two sets I need to "join" are, at the left hand side: > unit | token | exponent > ---+---+-- > m.s^-1 | m | 1 > m.s^-1 | s | -1 > m.s^-2 | m | 1 > m.s^-2 | s | -2 > And at the right hand side: > token | ex

Re: [GENERAL] How to match sets?

2009-09-13 Thread Ludwig Kniprath
Hello, this query on the two "tables" you suggested (named "test_left" and "test_right") returns the correct result without transformations: select distinct t1.unit from test_left as t1 inner join test_left as t2 on t1.unit = t2.unit and t1.token != t2.token and t1.exponent != t2.exponen

Re: [GENERAL] schema proxying virtual database

2009-09-13 Thread Stefan Kaltenbrunner
Rajesh Kumar Mallah wrote: Dear List, There are many opensource applications that support postgresql (eg , gforge , bricolage , dspam ..) but does not use schemas(namespaces) as a result of which you are forced to use/create a new database and loose the advantage of linking the application dat

[GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Daniel Schuchardt
Hy, i have some trouble with the new postgresql 8.4. we check out the compatibility between postgres 8.1 and 8.4 so we have the following error: invalid byte sequence for encoding "WIN1252": 0x00 can anyone say me a work-around? We have to change the escape chars that are inserted by our par

Re: [GENERAL] postgresql.key secure storage

2009-09-13 Thread John R Pierce
Saleem EDAH-TALLY wrote: This concerns use of postgresql.key private key file on the client side. psql can't establish a connection. with an encrypted postgresql.key file. If I'm wrong here, the following is invalid and please show me the steps I'm ignoring. An application using libpq would

Re: [GENERAL] schema proxying virtual database

2009-09-13 Thread Rajesh Kumar Mallah
thanks that sounds like a really easy & neat solution. On Sun, Sep 13, 2009 at 11:02 PM, Stefan Kaltenbrunner wrote: > Rajesh Kumar Mallah wrote: > >> Dear List, >> >> There are many opensource applications that support postgresql >> (eg , gforge , bricolage , dspam ..) but does not use schemas(

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Peter Eisentraut
On sön, 2009-09-13 at 18:51 +0200, Daniel Schuchardt wrote: > UPDATE belzeil_frei SET bz_zubez= '*', bz_zubez_rtf= > '{\\rtf1\\ansi\\deff0{\\fonttbl{\\f0\\fnil\\fcharset0 > Arial;}}\r\n\\viewkind4\\uc1\\pard\\lang1031\\fs20 *\r\n\\par }\r\n\0' > WHERE dbrid=295116 > > Result : ERROR: invalid b

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Scott Ribe
> In that example i try to insert a "*" with rtf-encoding. It's not the "*" causing the error, it's the "\0"--which I'm pretty sure is not a valid character for an RTF file either. Do you have an encoder which is just blindly reading through the null terminator of a C string and including it in th

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Daniel Schuchardt
Hy Scott, as wrote in my awnser to peter everything is working fine in Postgres81. So its not possible thats our parser. Please look in my awnser for peter. Scott Ribe schrieb: In that example i try to insert a "*" with rtf-encoding. It's not the "*" causing the error, it's the "\0"--whi

[GENERAL] Question on WAL/PITR

2009-09-13 Thread ReneMarxis
Hello i have one script that does a full backup weekly and one thats used to archive the WAL files. The script that does the full backup creates a new directory and stores the directory name to a config file. The script that copies the WAL files uses this configuration to store the files. What ha

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Daniel Schuchardt
First:In Postgres81 everything is working fine. Second:string:Not really: thats the orignal string, and its a string: (http://de.wikipedia.org/wiki/Rich_Text_Format) (http://en.wikipedia.org/wiki/Rich_Text_Format) {\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 Arial;}} \viewkind4\uc1\pard\lang

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Thomas Kellerer
Daniel Schuchardt wrote on 13.09.2009 18:51: UPDATE belzeil_frei SET bz_zubez= '*', bz_zubez_rtf= '{\\rtf1\\ansi\\deff0{\\fonttbl{\\f0\\fnil\\fcharset0 Arial;}}\r\n\\viewkind4\\uc1\\pard\\lang1031\\fs20 *\r\n\\par }\r\n\0' WHERE dbrid=295116 Result : ERROR: invalid byte sequence for encoding

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Peter Eisentraut
On sön, 2009-09-13 at 22:21 +0200, Daniel Schuchardt wrote: > First:In Postgres81 everything is working fine. In general, older versions of PostgreSQL treated encoding issues much mroe loosely, which subsequently lead to user errors, bugs, and confusion. Later versions are more strict. Therefore

Re: [GENERAL] "show all" command crashes server *** FIXED ***

2009-09-13 Thread Grant Maxwell
First of all thanks to those who provided input. This problem is now fixed and I thought I would post this solution so that others might benefit in the future. For the sake of completeness: The error was that if "show all" was run on this postgresql (version 8.3) server, postgres would cr

Re: [GENERAL] "show all" command crashes server *** FIXED ***

2009-09-13 Thread Tom Lane
Grant Maxwell writes: > The error was that if "show all" was run on this postgresql (version > 8.3) server, postgres would crash and then recover. > The postgres log showed: > Sep 10 23:55:36 theconsole postgres[31118]: [4-1] 0: LOG: 0: > server process (PID 31145) was te

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Daniel Schuchardt
I know you are true with definition's and standards, however, that code works for about 6 years ;o) Well, we will change our parser behavoir. We will check out that standard_conforming_strings parameter too but i see a lot of problems with our backup and restore system (plain text pg_dump's) a

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Daniel Schuchardt
Hi Thomas, thanks a lot we will check out that parameter. But if i understand it in the correct way that parameter will turn off all escape quoting. I have to check out, thanks a lot. Thomas Kellerer schrieb: Daniel Schuchardt wrote on 13.09.2009 18:51: UPDATE belzeil_frei SET bz_zubez= '*

Re: [GENERAL] postgresql.key secure storage

2009-09-13 Thread Marc Munro
On Sun, 2009-09-13 at 12:04 -0300, pgsql-general-ow...@postgresql.org wrote: > >A user must have the TRUNCATE privilege to truncate a table or be the > >tables owner. > > Well the TRUNCATE example I mentioned is perhaps not explicit of what > I meant > to say. A user who can modify data in a cli

Re: [GENERAL] invalid byte sequence for encoding

2009-09-13 Thread Peter Eisentraut
On Mon, 2009-09-14 at 00:36 +0200, Daniel Schuchardt wrote: > I know you are true with definition's and standards, however, that code > works for about 6 years ;o) > > Well, we will change our parser behavoir. We will check out that > standard_conforming_strings parameter too but i see a lot of