I would like to now if it is possible for PostgreSQL to make use of
multiple processes for a single query.
I am developing a data driven application which was a homemade plpgsql
function that identifies duplicate records(by single column) and
updates a boolean field (of these duplicates) as such.
On Fri, 2010-03-19 at 10:19 +0300, Allan Kamau wrote:
> I would like to now if it is possible for PostgreSQL to make use of
> multiple processes for a single query.
No.
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
C
Openbravo http://www.openbravo.com
Sunday Olutayo
Sadeeb Technologies Ltd
7 Mayegun Street, Ojo
Lagos State, Nigeria.
Tel: +234 1 7404524
D/L: +234 1 8169922
Cell: +234 8054600338
Fax: +234 8054895664
Email: olut...@sadeeb.com.ng
olut...@sadeeb.com
- Original Message -
From:
it's seems works
thansk
a++
On Thu, Mar 18, 2010 at 3:16 PM, Ashesh Vashi
wrote:
> Try to use libpqdll.lib instead of libpq.lib.
> --
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise Postgres Company
>
>
>
> On Thu, Mar 18, 2010 at 7:30 PM, elekis wrote:
>>
>> hi all,
>>
>>
>> I try to create a
Vikram Patil wrote:
> On AIX while starting postgresql server I got this error
> . But server starts up without any issues.
>
> LOG: could not bind IPv6 socket: Address already in use
>
> HINT: Is another postmaster already running on port 8432? If
> not, wait a few seconds and retry.
>
I get the following error when trying to create a view with the
following trivial example.
SQL error:
ERROR: rules on SELECT must have action INSTEAD SELECT
In statement:
CREATE VIEW "nutrition"."test_view" AS SELECT 2 as two, 3 as three
INTO TEMP temp_table; SELECT *,two+three as five FROM temp
Hey list,
I have a cron script that runs a couple cleanup commands on my
database. It runs three commands:
VACUUM ANALYZE;
CLUSTER;
REINDEX DATABASE "database";
They are run in the above order. I was wondering if there's a better
order to do this in. For example, should the ANALYZE be run _after_
yes, if you really want to do it - analyze should be running following
cluster, as it moves data around.
plus, with 8.4 autovacuum should do the job.
On 18/03/2010 23:18, Grant Allen wrote:
> Hi Raymond,
>
>> From a strictly relational viewpoint, this is as easy as
>
> (select users.uid, apps.appcode from apps, users)
> except
> (select canaccess.uid, canaccess.appcode from canaccess)
Joe & Grant, thanks for your replies... I knew it had to b
Hi,
We've been struggling with an MS Access 2007 app that updates a PG table. It
was working, and then it wasn't.
It looks like we recreated the table without specifying the precision on the
timestamp columns.
PG is defaulting to timestamp(6), which doesn't work with MS Access. The
finest p
Howdy folks,
I'm very happy to announce that the Postgres project has been selected
to
participate in this years Google Summer of Code program. Over the next couple
weeks we'll be looking to solidify our mentor base; if you work on Postgres
and would be willing to mentor a student, p
> VACUUM ANALYZE;
> CLUSTER;
> REINDEX DATABASE "database";
ANALYZE has to go after CLUSTER; and CLUSTER already
vacuums the tables (I'm not 100% sure though). CLUSTER also
reindexes the whole table, so there's no need for another REINDEX.
I think the right way of doing it would be:
CLUSTER;
ANA
Leonardo F escribió:
> > VACUUM ANALYZE;
> > CLUSTER;
> > REINDEX DATABASE "database";
>
> ANALYZE has to go after CLUSTER; and CLUSTER already
> vacuums the tables (I'm not 100% sure though). CLUSTER also
> reindexes the whole table, so there's no need for another REINDEX.
>
> I think the right
Hi,
I'm somewhat new to SQL so I need a bit of help with this problem. So
I have 2 tables: "selection" and "master", both have two columns in
each: "user_id" and "date".
The "selection" contains one row for each "user_id" and depicts _one_
"date" value for each user.
The "master" contains all "da
CORRECTION:
The original "selection" should be:
User1 2101
NOT
User1 19990101
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
The bigger problem is using time stamps to find the record for updating
Timestamps will not be unique as more than 1 record can have the same value
I suggest changing the updating method to use a unique key.
Message from mailto:douglas.lit...@orbitz.com "Little, Douglas"
douglas.lit...@orb
Thanks Laurence for Reply.
I can actually connect to server using network. I am just trying to
avoid this warning. Your solution for listen_address will work but I
want to keep it as "*" . Somehow it doesn't complain on any other *nix
Operation Systems.
Thanks & Regards,
Vikram
-Original Me
Hello!
I have to make a c function for determining if some point its inside a set
of elliptical geometries (I'm talking about a shared library, used like a
function in the queries ). The geometries are defined in a table, so the
function should iterate over a set of them. One option could be pass
On 03/19/2010 12:26 PM, Enzo Cappa wrote:
> Hello!
>
> I have to make a c function for determining if some point its inside a
> set of elliptical geometries (I'm talking about a shared library, used
> like a function in the queries ). The geometries are defined in a table,
> so the function should
On Fri, Mar 19, 2010 at 11:12 AM, jus...@magwerks.com
wrote:
>
> The bigger problem is using time stamps to find the record for updating
>
> Timestamps will not be unique as more than 1 record can have the same value
>
> I suggest changing the updating method to use a unique key.
MS-Access achiev
In anticipation of the release of PostgreSQL 9.0, it is once again time
to update the message translations. We are not very near a string
freeze yet, which has traditionally been associated with the first
release candidate, but I feel that things are already stable enough to
begin this work now.
When connected to ODBC source Access ignores locking steps. I don't think
that's the problem.
If memory serves, when Access is building the UPDATE command automatically the
WHERE clause includes every single column being updated when the old values,
something like this
Update set col =145, co
Dear List
I use plpgsql function as a postfix mailserver look-up table. For
example to look up virtual email address.
If I don't host this email address, then the function returns null.
Because it's a 1 row of null value postfix logs a warning message.
Although it's harmless in that postfix takes
On 19/03/2010 11:35 PM, Little, Douglas wrote:
The update can’t then locate the row (timestamp mismatch), and displays
the ‘write conflict’ error.
Change the ODBC driver settings to issue updates by primary key, and the
issue goes away. IIRC it's done in some backward-ish way like turning
of
2010/3/20 zhong ming wu :
> Dear List
>
> I use plpgsql function as a postfix mailserver look-up table. For
> example to look up virtual email address.
> If I don't host this email address, then the function returns null.
> Because it's a 1 row of null value postfix logs a warning message.
> Altho
Hello PG support,
Recently i am facing locale problem in postgres 8.3. In my home
machine i have 8.4 which have db schema as
CREATE DATABASE impulse_travel
WITH OWNER = postgres
ENCODING = 'UTF8'
LC_COLLATE = 'English_India.1252'
LC_CTYPE = 'English_India.1252'
26 matches
Mail list logo
