I expect that only changes on step 2.7 persisted in DB.
On Tue, May 4, 2010 at 11:18 PM, Scott Marlowe wrote:
> On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmailov
> wrote:
> > Hi,
> > I'm working on a solution that utilizes 2 phase commit protocol (between
> SQL
> > Server and PostgreSQL). No
On Wed, 2010-05-05 at 08:05 +0200, Gerd Koenig wrote:
> "$libdir/euc2004_sjis2004": No such file or directory
> STATEMENT: CREATE OR REPLACE FUNCTION euc_jis_2004_to_shift_jis_2004
> (INTEGER, INTEGER, CSTRING, INTERNAL, INTEGER) RETURNS VOID AS
> '$libdir/euc2004_sjis2004', 'euc_jis_2004_to_shi
Hi Shoaib,
thanks for your hint it solved the problem just by "yum update postgresql-*"
since I had the correct repository already ;-)
regards...GERD...
On Wednesday 05 May 2010 08:28:08 am Shoaib Mir wrote:
> On Wed, May 5, 2010 at 4:05 PM, Gerd Koenig wrote:
> > Hello,
> >
> > I've tried to
On Wed, May 5, 2010 at 4:05 PM, Gerd Koenig wrote:
> Hello,
>
> I've tried to install the latest 9.0Beta (Fedora12, pgdg repository), but
> with
> no success. "initdb" returns with an error described below.
>
>
> blub#> yum list postgres*
>
Hello,
I've tried to install the latest 9.0Beta (Fedora12, pgdg repository), but with
no success. "initdb" returns with an error described below.
blub#> yum list postgres*
Loaded plugins: refresh-packagekit
Installed Packages
postgresql.i3
On Tue, May 4, 2010 at 11:52 PM, Konstantin Izmailov wrote:
> Hi,
> I'm working on a solution that utilizes 2 phase commit protocol (between SQL
> Server and PostgreSQL). Normally PostgreSQL statements sequense is:
> 1. START
> 2.
> 3. PREPARE TRANSACTION 'uuid'
> 4. COMMIT PREPARED 'uuid'
>
> Wh
Hi,
I'm working on a solution that utilizes 2 phase commit protocol (between SQL
Server and PostgreSQL). Normally PostgreSQL statements sequense is:
1. START
2.
3. PREPARE TRANSACTION 'uuid'
4. COMMIT PREPARED 'uuid'
What if on step 2 user application issues statements with SAVEPOINTs, e.g.
2.1.
AI Rumman wrote:
I have configured SSL connection between client/server using
self-signed certificate.
...
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
.
I set the $PGSSLMODE=require to encrypt data across the netwrok.
How could I be sure that data is encrypted over the network?
I have configured SSL connection between client/server using self-signed
certificate.
--
Password:
Welcome to psql 8.3.8, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for hel
We have a production database that contains data which is easily
recreated at runtime. I'm considering upgrading this to 9.0 beta1 to
get some experience with the new hot standby system on a server that
is under medium to heavy load.
Obviously, being a production database, it's inconvenient if th
Andre Lopes writes:
> Thanks for the reply. I have not call it STRICT...
Yes you are:
> RETURNS NULL ON NULL INPUT
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
Hi,
Thanks for the reply. I have not call it STRICT...
The function is:
[code]
CREATE OR REPLACE FUNCTION "apr_insert_hist_2_1" (IN pNOME_VIEW varchar, IN
pCHAVE_1 varchar, IN pVAL_CHAVE_1 varchar, IN pVAL_CHAVE_2 date, IN
pVAL_CAMPO1 date, IN pVAL_COMENT varchar)
RETURNS void AS
$BODY$
DEC
On 5/05/2010 5:27 AM, Alvaro Herrera wrote:
pgsql wrote:
Hi,
one of our pgsql instances recently started to segfault multiple times a
week. I tried a couple of things to pin it down to a certain query
or job but failed to find any pattern. All I can offer is some notes
and a set of similar look
pgsql writes:
> one of our pgsql instances recently started to segfault multiple times a
> week. I tried a couple of things to pin it down to a certain query
> or job but failed to find any pattern. All I can offer is some notes
> and a set of similar looking back traces.
BTW, there is a post-8.3
pgsql writes:
> one of our pgsql instances recently started to segfault multiple times a
> week. I tried a couple of things to pin it down to a certain query
> or job but failed to find any pattern. All I can offer is some notes
> and a set of similar looking back traces.
All of those traces seem
Andre Lopes writes:
> If I use NULL in any parameter the function does not RAISE any NOTICE. I
> can't pass NULL values in parameters?
Sure you can. Maybe you declared the function STRICT? That means to
not call it for a NULL.
regards, tom lane
--
Sent via pgsql-gener
Hi,
I have a function, that I'm debugging...
If I use NULL in any parameter the function does not RAISE any NOTICE. I
can't pass NULL values in parameters?
[code]
select apr_ins_gder_2_1
('table_fgh' /* Varchar */,
'id_fgh' /* Varchar */,
'5' /* Varchar */,
NULL /* Date */,
'2001-01-05' /* Date
Thanks. I got working.
Best Regards,
On Tue, May 4, 2010 at 10:25 PM, Adrian Klaver wrote:
> On Tuesday 04 May 2010 1:55:35 pm Andre Lopes wrote:
> > HI,
> >
> > I have a PLPgSQL function that return void but I need to exit the
> function
> > if some condition returns true.
> >
> > I have tried
pgsql wrote:
> Hi,
>
> one of our pgsql instances recently started to segfault multiple times a
> week. I tried a couple of things to pin it down to a certain query
> or job but failed to find any pattern. All I can offer is some notes
> and a set of similar looking back traces.
Please install th
On Tuesday 04 May 2010 1:55:35 pm Andre Lopes wrote:
> HI,
>
> I have a PLPgSQL function that return void but I need to exit the function
> if some condition returns true.
>
> I have tried to do this, but I got an error:
>
> [code]
> IF pVAL_CHAVE_2 > pVAL_CAMPO1 THEN
> RAISE NO
Hi,
one of our pgsql instances recently started to segfault multiple times a
week. I tried a couple of things to pin it down to a certain query
or job but failed to find any pattern. All I can offer is some notes
and a set of similar looking back traces.
Thanks in advance.
Machine details
---
HI,
I have a PLPgSQL function that return void but I need to exit the function
if some condition returns true.
I have tried to do this, but I got an error:
[code]
IF pVAL_CHAVE_2 > pVAL_CAMPO1 THEN
RAISE NOTICE 'O campo data fim tem de ser maior que o campo data
inicio.';
sunpeng writes:
> after i execute "select count(*) from pois group by catcode";
> the log of query.targetList is :
> why there is the second TARGETENTRY? what's the purpose of the second
> TARGETENTRY?
It's the GROUP BY expression. Note the ressortgroupref and resjunk
settings.
I've the table
CREATE TABLE pois
(
uid integer not null,
name VARCHAR(128),
catcode VARCHAR(32) not null,
catname VARCHAR(32),
others VARCHAR(32)
);
after i execute "select count(*) from pois group by catcode";
the log of query.targetList is :
:targetList (
{TARGETENTRY
Vincenzo Romano wrote:
> Hi all.
>
> I'm willing to change an BIGINT ID column (actually a SERIAL8) with a
> BIGINT whose valules are (pseudo)random.
> The main objective is to avoid guessability.
> I whish I could also use it as the PK (as it's now) but that's not
> really important now.
> Any hi
Hi,
On 04.05.2010 18:24, Sergey E. Koposov wrote:
> ## select id ,count(*) from tmpx group by (id) having count(*)>1;
> id | count
> +---
> 0.519465064629912 | 2
> 0.0100625408813357 | 2
> 0.394671014975756 | 2
> (3 rows)
>
> and
> ## selec
On Tue, 4 May 2010, Tom Lane wrote:
## select id ,count(*) from tmpx group by (id) having count(*)>1;
id | count
+---
0.519465064629912 | 2
0.0100625408813357 | 2
0.394671014975756 | 2
(3 rows)
and
## select id from tmpx where id >
"Sergey E. Koposov" writes:
> On Tue, 4 May 2010, Tom Lane wrote:
>> They aren't; or at least you've not provided any evidence that they were.
> I think I did, since:
> ## select id ,count(*) from tmpx group by (id) having count(*)>1;
> id | count
> +---
Hi all.
I'm willing to change an BIGINT ID column (actually a SERIAL8) with a
BIGINT whose valules are (pseudo)random.
The main objective is to avoid guessability.
I whish I could also use it as the PK (as it's now) but that's not
really important now.
Any hint?
--
Vincenzo Romano
NotOrAnd Info
On Tue, 4 May 2010, Tom Lane wrote:
"Sergey E. Koposov" writes:
So among 10^5 random numbers there are already 3 collisions. Which doesn't
seem right for the function which generate randoms of double precision
The underlying random() function only generates 31-bit integers, so
Okay, the fa
On Tuesday 4. May 2010 18.05.02 Tom Lane wrote:
> Leif Biberg Kristensen writes:
> > Another point: I'm uncertain how to define a «user» in this context.
Someone
> > who wants to highlight plpgsql code snippets is most likely to be some
kind of
> > developer.
>
> Sure, but what I meant was "n
Message from mailto:m...@sai.msu.ru "Sergey E. Koposov" m...@sai.msu.ru
at 05-04-2010 06:36:23 PM --
Hello,
I'm getting strange results with PostgreSQL random() function. It would be
great if someone could either show where I am wrong or PG is wrong. Here
is what I do (PG 8.4.3, x86_
Leif Biberg Kristensen writes:
> On Tuesday 4. May 2010 16.31.20 Tom Lane wrote:
>> There's an awful lot of them, many of which aren't really intended to be
>> called by users anyway. Can't you just do "if it looks syntactically
>> like a function call, assume it is one"?
> Another point: I'm un
Hi,
I am working on adding some functionality to pgTAP, in order to detect
unintended data modification side-effects.
The idea is to,
1. store the insert/update counts for all tables in a temporary table,
2. then run the test unit in a subtransaction,
3. then compare the new insert/update counts
"Sergey E. Koposov" writes:
> So among 10^5 random numbers there are already 3 collisions. Which doesn't
> seem right for the function which generate randoms of double precision
The underlying random() function only generates 31-bit integers, so
collisions aren't as improbable as they might seem
Leif Biberg Kristensen wrote:
> On Tuesday 4. May 2010 16.31.20 Tom Lane wrote:
> > Leif Biberg Kristensen writes:
> > > Now I only need a list of the built-in functions.
> >
> > There's an awful lot of them, many of which aren't really intended to be
> > called by users anyway. Can't you just d
On Tuesday 4. May 2010 16.31.20 Tom Lane wrote:
> Leif Biberg Kristensen writes:
> > Now I only need a list of the built-in functions.
>
> There's an awful lot of them, many of which aren't really intended to be
> called by users anyway. Can't you just do "if it looks syntactically
> like a func
Hello,
I'm getting strange results with PostgreSQL random() function. It would be
great if someone could either show where I am wrong or PG is wrong. Here
is what I do (PG 8.4.3, x86_64 platform);
I basically try to create the table with the column filled with random
numbers (either integer
On Tuesday 4. May 2010 16.31.20 Tom Lane wrote:
> Leif Biberg Kristensen writes:
> > Now I only need a list of the built-in functions.
>
> There's an awful lot of them, many of which aren't really intended to be
> called by users anyway. Can't you just do "if it looks syntactically
> like a func
On 5/4/2010 9:37 AM, Tom Lane wrote:
Andy Colson writes:
On 5/3/2010 9:44 PM, Tom Lane wrote:
I'm not immediately seeing a simple way to improve this.
How about building a statically linked psql in 'make check', just for
pg_regress to use?
[ shrug... ] That sort of defeats the purpose of
the rule of thumb for me is:
- if you have more than one column as PK - and are variable length,
or more than 2 columns, fixed length, no bigger than 8 bytes - go for
surrogate - always.
- if PK is variable length, on average longer than 8 bytes, or can
change - go surrogate.
- Otherwise leave
Andy Colson writes:
> On 5/3/2010 9:44 PM, Tom Lane wrote:
>> I'm not immediately seeing a simple way to improve this.
> How about building a statically linked psql in 'make check', just for
> pg_regress to use?
[ shrug... ] That sort of defeats the purpose of testing the binaries
we are inten
2010/5/4 Grzegorz Jaśkiewicz :
>
> Another thing, If your PK changes, it is no longer a PK, you can't rely on it.
Depending upon what you mean by changes this could be true or it could
be a matter of opinion. If your referring to a candidate key's value
changes, this key still provides a useful w
Leif Biberg Kristensen writes:
> Now I only need a list of the built-in functions.
There's an awful lot of them, many of which aren't really intended to be
called by users anyway. Can't you just do "if it looks syntactically
like a function call, assume it is one"?
regar
On Tue, May 4, 2010 at 3:16 PM, Merlin Moncure wrote:
> On Tue, May 4, 2010 at 9:40 AM, Merlin Moncure wrote:
>> On Sat, May 1, 2010 at 4:14 PM, John R Pierce wrote:
>>>
>>> If your 'natural key' is a large text field, I'd have to assume there's some
>>> point at which a surrogate index would be
- Original Message -
From: Devrim GÜNDÜZ
Date: Tue, 04 May 2010 07:18:47 +0300
Subject: Re: [GENERAL] Latest source RPMs for 8.1.20
To: Justin Pasher
CC: pgsql-general@postgresql.org
On Mon, 2010-05-03 at 10:49 -0500, Justin Pasher wrote:
I'm looking for the latest source RPMs for
On Tue, May 4, 2010 at 9:40 AM, Merlin Moncure wrote:
> On Sat, May 1, 2010 at 4:14 PM, John R Pierce wrote:
>>
>> If your 'natural key' is a large text field, I'd have to assume there's some
>> point at which a surrogate index would be more efficient. Would this be
>> above a few dozen characte
Sir,
The problem has solved. Thank You so much.
Regards
Gloier
On Tue, May 4, 2010 at 1:00 AM, jus...@magwerks.com wrote:
> Postgresql account does not need to own the directory just have full
> control. If you can't change security settings or take/assign ownership
> then the account doing t
On 5/3/2010 9:44 PM, Tom Lane wrote:
I wrote:
I'd have thought that pg_regress would have a more obvious failure if it
was trying to use an old libpq.so version though --- it should have
looked similar to what you referenced for pg_dump, for instance.
I think I see what's going on here. pg_re
On Sat, May 1, 2010 at 4:14 PM, John R Pierce wrote:
>
> If your 'natural key' is a large text field, I'd have to assume there's some
> point at which a surrogate index would be more efficient. Would this be
> above a few dozen characters, or a few 100 characters? I wouldn't want a
> PK based o
On Tue, May 04, 2010 at 05:12:16PM +0600, AI Rumman wrote:
> I change the pg_hba.conf as below:
and you restart or do a pg_ctl reload?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thanks a lot, this helped me with the messages. I thought, I would only have to
define a operator class that fullfills at least the equals strategy. I didn't
know, that I would have to provide a "full" btree operator class.
Best regards
Carsten Kropf
Am 03.05.2010 um 15:56 schrieb Tom La
I change the pg_hba.conf as below:
hostssl allall10.0.0.34/32 md5
But still the same problem.
On Tue, May 4, 2010 at 5:03 PM, Thom Brown wrote:
> On 4 May 2010 11:50, AI Rumman wrote:
>
>> I have created server.crt and server.key using the Postgresql
>> documentation.
>>
>> F
m...@kitchenpc.com (Mike Christensen) writes:
> I have a table that stores a user ID and a subscription type, and this is
> really all it needs to store and any pair of values will always be unique. In
> fact, I think this pair should be the primary key on the table. However, I'm
> using Castle A
On 4 May 2010 11:50, AI Rumman wrote:
> I have created server.crt and server.key using the Postgresql
> documentation.
>
> Followings are the commands:
> ---
> openssl req -new -text -out server.req
>
> openssl rsa -in privkey.pem -out server.key
> rm privk
I have created server.crt and server.key using the Postgresql documentation.
Followings are the commands:
---
openssl req -new -text -out server.req
openssl rsa -in privkey.pem -out server.key
rm privkey.pem
openssl req -x509 -in server.req -text -key serv
On 4 May 2010 10:42, AI Rumman wrote:
> I have my postgresql 8.3.8 database and application server in the same
> network over the WAN.
> I need to enable data encryption using SSL.
>
> Is there any step-by-step guide to complete this task?
>
You can try this guide:
http://www.ibm.com/developerwo
I have my postgresql 8.3.8 database and application server in the same
network over the WAN.
I need to enable data encryption using SSL.
Is there any step-by-step guide to complete this task?
On Tue, 2010-05-04 at 13:32 +0600, AI Rumman wrote:
> How can I be sure that Postgresql Server has been installed with
> open-ssl support?
You can check postgres binary with ldd, I think. i.e.:
$ ldd /usr/bin/postgres|grep ssl
libssl.so.10 => /usr/lib/libssl.so.10 (0x07b43000)
--
Devri
2010/5/4 Peter Eisentraut :
> On tis, 2010-05-04 at 09:19 +0100, Grzegorz Jaśkiewicz wrote:
>> 2010/5/3 Peter Eisentraut :
>> > It was a convenient choice. You could propose a different method for
>> > generating the specific routine name, but given that it has to fit into
>> > an identifier and h
On tis, 2010-05-04 at 09:19 +0100, Grzegorz Jaśkiewicz wrote:
> 2010/5/3 Peter Eisentraut :
> > It was a convenient choice. You could propose a different method for
> > generating the specific routine name, but given that it has to fit into
> > an identifier and has to allow for function overloadi
2010/5/3 Peter Eisentraut :
> It was a convenient choice. You could propose a different method for
> generating the specific routine name, but given that it has to fit into
> an identifier and has to allow for function overloading, some kind of
> number makes the most sense, in absence of any othe
Thanks for the reply,
It is working now.
Best Regards.
On Tue, May 4, 2010 at 7:44 AM, Maximilian Tyrtania <
maximilian.tyrta...@byte-employer.de> wrote:
> Am 03.05.2010 um 23:50 schrieb Andre Lopes:
>
> > Thanks for the reply's,
> >
> > I need to do a Dynamic SELECT INTO. There is a way of do
On Tuesday 4. May 2010 08.20.56 Yeb Havinga wrote:
> Leif Biberg Kristensen wrote:
> > Now I only need a list of the built-in functions. There doesn't seem to be
a
> > pg_get functions()?
> >
> Try psql -E postgres
> (-E shows all queries psql does on the catalog)
>
> then \df
Thanks, Yeb.
On 04/05/10 1:02 PM, AI Rumman wrote:
How can I be sure that Postgresql Server has been
installed with open-ssl support?
Any help please.
Execute following command:
pg_config|grep ssl
Above command should show following option:
CONFIGURE = '--prefix=/home/edb/AS83R2/build/AS83R2/edb-postgr
On 04/05/10 1:02 PM, AI Rumman wrote:
How can I be sure that Postgresql Server has been
installed with open-ssl support?
Any help please.
Execute following command:
pg_config|grep ssl
Above command should show following option:
CONFIGURE = '--prefix=/home/edb/AS83R2/build/AS83R2/edb-postgr
How can I be sure that Postgresql Server has been installed with open-ssl
support?
Any help please.
Is it possible to send encrypted text at all the nodes in replication mode
for PGPOOL II 2.3.3?
Any help please.
68 matches
Mail list logo
