Hi,
As part of datamining activity. I have some plpgsql functions
(executed in parallel, up to 6 such concurrent calls) that perform
some reads and writes of large number of (maybe 1) records at a
time to a table having multi-column primary key.
It seems the writing of these few thousands recor
ray wrote:
I just downloaded 9.0 onto my laptop and desktop Windows XP machines.
Nether one could run the stack builder. Windows would fault any time
I tried to run it. I tried inputing the proxy server but that did not
help.
I have found many tutorials but none look like the 9.0. Many seem
I just downloaded 9.0 onto my laptop and desktop Windows XP machines.
Nether one could run the stack builder. Windows would fault any time
I tried to run it. I tried inputing the proxy server but that did not
help.
I have found many tutorials but none look like the 9.0. Many seem to
be for Ente
On 11/10/10 6:08 PM, Devrim GÜNDÜZ wrote:
On Wed, 2010-11-10 at 09:30 -0800, Jason wrote:
Is 8.2.3 still available anywhere on the PostgreSQL site? I couldn't
find it.
Please check ftp-archives.postgresql.org
ah, its back up now
ftp://ftp-archives.postgresql.org/pub/source/v8.2.3/
--
Se
On Wed, 2010-11-10 at 09:30 -0800, Jason wrote:
>
> Is 8.2.3 still available anywhere on the PostgreSQL site? I couldn't
> find it.
Please check ftp-archives.postgresql.org
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpm
On Nov 10, 2010, at 4:30 PM, Daniel Verite wrote:
> Filonenko Michael wrote:
>
>> I create simple mechanism to inform user about something in database
>> triggers. In my front-end I use PQsetNoticeReceiver, and display messages
>> in QTextEdit.
>> I think about multi-user environment.
Filonenko Michael wrote:
> I create simple mechanism to inform user about something in database
> triggers. In my front-end I use PQsetNoticeReceiver, and display messages
> in QTextEdit.
> I think about multi-user environment. I read about NOTIFY/LISTEN, but find
> no callback mecha
"Marc Mamin" writes:
> I'm experimenting with dblink, and have an issue with async. queries
> that do not return result sets.
> (Postgres 8.3.9)
> --youll need your own connect string to repeat:
> select dblink_connect_u('myconn1', 'hostaddr=127.0.0.1 port=5432
> dbname=postgres user=postgres
"Filonenko Michael" writes:
> I create simple mechanism to inform user about something in database
> triggers. In my front-end I use PQsetNoticeReceiver, and display messages
> in QTextEdit.
> I think about multi-user environment. I read about NOTIFY/LISTEN, but find
> no callback mechanism.
Hello.
I create simple mechanism to inform user about something in database
triggers. In my front-end I use PQsetNoticeReceiver, and display messages
in QTextEdit.
I think about multi-user environment. I read about NOTIFY/LISTEN, but find
no callback mechanism. Is it planning?
--
With be
On Tue, Nov 9, 2010 at 1:51 PM, Igor Neyman wrote:
> > -Original Message-
> > From: AI Rumman [mailto:rumman...@gmail.com]
> > Sent: Tuesday, November 09, 2010 3:26 AM
> > To: pgsql-general General
> > Subject: REINDEX requirement?
> >
> > How do I know that index require REINDEX?
> >
> >
On Tue, Nov 9, 2010 at 1:36 PM, Sandeep Srinivasa wrote:
>
> On Tue, Nov 9, 2010 at 11:46 PM, David Boreham wrote:
>>
>>
>> Hmm...typically multi-core scaling issues are in the area of memory
>> contention and cache coherence (and therefore are for the most part not
>> dependent on the OS and its
Hi,
Is there anything like MySQL workbench for PostgreSQL?
I know there are a few alternatives, but was hoping to hear specific choices
and not just some random anonymous internet list like the ones i have been
reading.
What i need is something powerful enough to connect to an existing
PostgreSQ
Fujii, thank you very much for this clarification.
Regards,
Dan
-Original Message-
From: Fujii Masao [mailto:masao.fu...@gmail.com]
Sent: 09 November 2010 11:55
To: Daniel Harris
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Failed archive_command copy - number of attempts
con
On 10 Nov 2010, at 18:30, Jason wrote:
> Thanks for the replies.
>
> Yes - we're aware that there are newer versions of PostgreSQL out there. If
> it were completely up to us we would be using 8.2.18 or even 8.4. The
> problem is - we need to install on a network that has a rather involved
> ap
Jason writes:
> Yes - we're aware that there are newer versions of PostgreSQL out there. If
> it were completely up to us we would be using 8.2.18 or even 8.4. The
> problem is - we need to install on a network that has a rather involved
> approval process for all software tools that are introdu
On 10 November 2010 17:30, Jason wrote:
>
> Thanks for the replies.
>
> Yes - we're aware that there are newer versions of PostgreSQL out there. If
> it were completely up to us we would be using 8.2.18 or even 8.4. The
> problem is - we need to install on a network that has a rather involved
>
"Markus Wollny" writes:
> I currently testing the upgrade of our 8.3 databases to 9.0.
> In some of those restored databases to_tsquery is throwing an error:
> magazine=# SELECT to_tsquery('simple','plants');
> ERROR: invalid input syntax for type oid: "simple"
So far as I can see offhand, the
On 11/10/10 9:30 AM, Jason wrote:
Thanks for the replies.
Yes - we're aware that there are newer versions of PostgreSQL out there. If
it were completely up to us we would be using 8.2.18 or even 8.4. The
problem is - we need to install on a network that has a rather involved
approval process f
On 10/11/2010 17:30, Jason wrote:
Thanks for the replies.
Yes - we're aware that there are newer versions of PostgreSQL out there. If
it were completely up to us we would be using 8.2.18 or even 8.4. The
problem is - we need to install on a network that has a rather involved
approval process
On Wed, Nov 10, 2010 at 09:30:46AM -0800, Jason wrote:
>
> Thanks for the replies.
>
> Yes - we're aware that there are newer versions of PostgreSQL out there. If
> it were completely up to us we would be using 8.2.18 or even 8.4. The
> problem is - we need to install on a network that has a ra
Bill Moran writes:
> We have some processes that have proved themselves to cause
> ridiculous amounts of table/index bloat above and beyond what
> autovac can manage.
Sure you can't fix that with some table-specific autovacuum settings?
regards, tom lane
--
Sent via pg
We have an application that is using dblink from within trigger
procedures to send data to other postgres databases. Its implementing
a highly application specific sort of data replication.
My developers are complaining about the lack of support for 2 phase
commit in this scenario.Can we
Thanks for the replies.
Yes - we're aware that there are newer versions of PostgreSQL out there. If
it were completely up to us we would be using 8.2.18 or even 8.4. The
problem is - we need to install on a network that has a rather involved
approval process for all software tools that are intr
Raymond O'Donnell wrote:
> On 10/11/2010 16:31, Jason wrote:
>>
>> Hi - I'm trying to find where I can download PostgreSQL 8.2.3.
>>
>> I've looked on the PostgreSQL website but I do not see version 8.2.3
>> specifically.
>
> I'm sure you're going to get a tonne of replies pointing out that you
> (Postgres 8.3.9)
oops, this is actually 8.4.4 on Windows.
-Original Message-
From: Marc Mamin
Sent: Mittwoch, 10. November 2010 18:25
To: 'pgsql-general@postgresql.org'
Subject: dblink_get_result issue
Hello,
I'm experimenting with dblink, and have an issue with async. queries
that d
Hi!
I currently testing the upgrade of our 8.3 databases to 9.0.
In some of those restored databases to_tsquery is throwing an error:
magazine=# SELECT to_tsquery('simple','plants');
ERROR: invalid input syntax for type oid: "simple"
LINE 1: SELECT to_tsquery('simple','plants');
In other datab
Hello,
I'm experimenting with dblink, and have an issue with async. queries
that do not return result sets.
(Postgres 8.3.9)
--youll need your own connect string to repeat:
select dblink_connect_u('myconn1', 'hostaddr=127.0.0.1 port=5432
dbname=postgres user=postgres password=x');
select dbl
We have some processes that have proved themselves to cause
ridiculous amounts of table/index bloat above and beyond what
autovac can manage.
The good news is that this is very predictable in the application
and cause by background processes that can afford to take a little
extra time to clean u
On 11/10/10 8:31 AM, Jason wrote:
Hi - I'm trying to find where I can download PostgreSQL 8.2.3.
I've looked on the PostgreSQL website but I do not see version 8.2.3
specifically.
Any help would be appreciated.
thats a rather old (feb 2007) and fairly buggy release. 8.2.18 is the
current 8
On 10/11/2010 16:31, Jason wrote:
Hi - I'm trying to find where I can download PostgreSQL 8.2.3.
I've looked on the PostgreSQL website but I do not see version 8.2.3
specifically.
I'm sure you're going to get a tonne of replies pointing out that you
should use 8.2.18, which is 15 releases' w
Hi - I'm trying to find where I can download PostgreSQL 8.2.3.
I've looked on the PostgreSQL website but I do not see version 8.2.3
specifically.
Any help would be appreciated.
Thanks,
Jason
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/PostgreSQL-8-2-3-tp3258962p32
On Nov 10, 2010, at 2:55 PM, pasman pasmański wrote:
> How to add comment on table with calculated value ?
>
> COMMENT ON TABLE test IS 'Updated ' || current_date;
You can create function to do that.
Or
If you are using PG9.0, then DO would help you, as given below:
do $$
Declare
t text;
be
I have a query that looks like this...:
select * from table where field is null
And when I run explain, it tells me that it uses seq scan... Is this because pg
thinks that seq scan is as fast as using indexes or because using index on "is
null" queries does
not work?
Regards,
BTJ
--
--
On Wed, 10 Nov 2010 10:00:43 -0500
Tom Lane wrote:
> =?ISO-8859-1?Q?Bj=F8rn?= T Johansen writes:
> > I have a query that looks like this...:
> > select * from table where field is null
>
> > And when I run explain, it tells me that it uses seq scan... Is this
> > because pg thinks that seq sca
=?ISO-8859-1?Q?Bj=F8rn?= T Johansen writes:
> I have a query that looks like this...:
> select * from table where field is null
> And when I run explain, it tells me that it uses seq scan... Is this because
> pg thinks that seq scan is as fast as using indexes or because using index on
> "is nu
2010/11/10 Bjørn T Johansen :
> select * from table where field is null
>
> And when I run explain, it tells me that it uses seq scan... Is this because
> pg thinks that seq scan is as fast as using indexes or because using index on
> "is null" queries does
> not work?
>
Does the table have *lot
2010/11/10 pasman pasmański
> Hello.
>
>
> How to add comment on table with calculated value ?
>
> COMMENT ON TABLE test IS 'Updated ' || current_date;
>
> not works ...
>
>
Hi,
I'd suggest something like this:
do $$
begin
execute 'COMMENT ON TABLE test_count is ''Updated ' || current_date ||
Hello.
How to add comment on table with calculated value ?
COMMENT ON TABLE test IS 'Updated ' || current_date;
not works ...
Regards.
pasman
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/ma
39 matches
Mail list logo
