[GENERAL] Re: psql error: psql: symbol lookup error: psql: undefined symbol: PQconnectdbParams

2011-12-29 Thread hosuresh
Tanks a lot to all... Finally i got the solution... my postgres working fine on server... - Regards, Suresh Hosur -- View this message in context: http://postgresql.1045698.n5.nabble.com/psql-error-psql-symbol-lookup-error-psql-undefined-symbol-PQconnectdbParams-tp5104950p5107139.h

[GENERAL] Refine Form of My querry

2011-12-29 Thread saqib11
Hi every1 how are u all??? Members i am new in postgres and want to work on pgrouting but i am facing some issue with it. Will u please help me??? I have loaded my line shapefile in pgadmin environment, which creates a table name 'Route', but when i made a query 'Create View' at it, it will sh

Re: [GENERAL] Refine Form of My querry

2011-12-29 Thread John R Pierce
On 12/29/11 2:11 AM, saqi...@igis.nust.edu.pk wrote: I am sending my problems with attachment please have a look at this.. please don't send attachments to email lists. -- john r pierceN 37, W 122 santa cruz ca mid-left coast -- Sent via

Re: [GENERAL] Refine Form of My querry

2011-12-29 Thread Eduardo Morras
At 11:11 29/12/2011, you wrote: Hi every1 how are u all??? Members i am new in postgres and want to work on pgrouting but i am facing some issue with it. Will u please help me??? I have loaded my line shapefile in pgadmin environment, which creates a table name 'Route', but when i made a query 'C

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Adrian Klaver
On 12/29/2011 09:19 AM, Merlin Moncure wrote: I'll pass, thanks for all your "help" guys. It's been a blast. I did not suggest that. I suggested they *might* be happening. In lieu of a reproducible test case (a couple of us took a stab at creating one ourselves and could not come up with y

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Merlin Moncure
On Thu, Dec 29, 2011 at 10:20 AM, Greg Donald wrote: > On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane wrote: >>> < SELECT pg_catalog.setval('cp_state_id_seq', 52, true); >>> > SELECT pg_catalog.setval('cp_state_id_seq', 1, false); >> >> These "grep" calls are showing just exactly not enough to prove >

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Adrian Klaver
On 12/29/2011 08:13 AM, Greg Donald wrote: On Wed, Dec 28, 2011 at 4:58 PM, Adrian Klaver wrote: What is the pg_dump command, with options, you are using? My backup shell script contains: /usr/bin/pg_dump cp | bzip2> $FILE One possible issue that I see is the lack of explicit options. Giv

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Greg Donald
On Wed, Dec 28, 2011 at 4:58 PM, Adrian Klaver wrote: > What is the pg_dump command, with options, you are using? My backup shell script contains: /usr/bin/pg_dump cp | bzip2 > $FILE -- Greg Donald -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Merlin Moncure
On Thu, Dec 29, 2011 at 10:53 AM, Greg Donald wrote: > On Thu, Dec 29, 2011 at 10:27 AM, Merlin Moncure wrote: >> if you take a bzipped schema only dump (pg_dump -s), I'd be happy to >> look it over and eliminate the 'operator error' class of issues that >> Tom is thinking might be happening.  pr

[GENERAL] Postgresql Replication Comparison Required

2011-12-29 Thread saurabh gupta
I am doing POC on Posgtresql replication. I am using latest version of postgresql i.e. 9.1. There are multiple replication solutions avaliable in the market (PGCluster, Pgpool-II, Slony-I). Postgresql also provide in-built replication solutions (Streaming replication, Warm Standby and hot standby).

Re: [GENERAL] Unable to Increase the column which was part of Primary key

2011-12-29 Thread Andreas Kretschmer
karthikeyan wrote: > Hi, > > I am trying to increase size of the column which was/is part of the Primary. > > Exiting table > CREATE TABLE test_dim_store > ( > storek integer NOT NULL DEFAULT > nextval('dim_store_storek_seq1'::regclass), > retailerk character varying(10) NOT NULL, > store

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Greg Donald
On Thu, Dec 29, 2011 at 10:27 AM, Merlin Moncure wrote: > if you take a bzipped schema only dump (pg_dump -s), I'd be happy to > look it over and eliminate the 'operator error' class of issues that > Tom is thinking might be happening.  private mail is ok. Operator error? Wow.. so now I'm doing

[GENERAL] Verifying a timestamp is null or in the past

2011-12-29 Thread Alexander Farber
Hello fellow postgres users, in my game using PostgreSQL 8.4.9 players can purchase a VIP ("very important person") status: # \d pref_users; Table "public.pref_users" Column |Type | Modifiers +-+---

Re: [GENERAL] Refine Form of My querry

2011-12-29 Thread David Salisbury
On 12/29/11 3:11 AM, saqi...@igis.nust.edu.pk wrote: Hi every1 how are u all??? Members i am new in postgres and want to work on pgrouting but i am facing some issue with it. Will u please help me??? I have loaded my line shapefile in pgadmin environment, which creates a table name 'Route', but

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Greg Donald
On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane wrote: > These "grep" calls are showing just exactly not enough to prove > anything.  I remain unclear as to what state is actually in the > database, or what is being dumped, but I suspect at this point that you > may have multiple sequences of the same n

Re: [GENERAL] PostgreSQL 9.1 pg_dump setval() sets wrong value

2011-12-29 Thread Greg Donald
On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane wrote: >> < SELECT pg_catalog.setval('cp_state_id_seq', 52, true); >> > SELECT pg_catalog.setval('cp_state_id_seq', 1, false); > > These "grep" calls are showing just exactly not enough to prove > anything. Those grep calls prove my old backups with 8.4 p

Re: [GENERAL] Verifying a timestamp is null or in the past

2011-12-29 Thread Andreas Kretschmer
Alexander Farber wrote: > Hello fellow postgres users, > > in my game using PostgreSQL 8.4.9 players can > purchase a VIP ("very important person") status: > > # \d pref_users; > Table "public.pref_users" >Column |Type | Modifiers > +-

Re: [GENERAL] Postgresql Replication Comparison Required

2011-12-29 Thread Gabriele Bartolini
Hello, in general my advice would be to stick with native features, therefore use either Streaming Replication (or alternatively log shipping replication). You might need some tools to help you manage the cluster, clients routing and balancing but I suggest you look into this later. On Thu,

Re: [GENERAL] Verifying a timestamp is null or in the past

2011-12-29 Thread Alexander Farber
Thank you Andreas - now that one case works ok, On Thu, Dec 29, 2011 at 7:44 PM, Andreas Kretschmer wrote: > Try "if (not coalesce(has_vip, false)) then ..." but the other case not: # create or replace function pref_move_week(_from varchar, _to varchar) returns void as $BODY$

Re: [GENERAL] Verifying a timestamp is null or in the past

2011-12-29 Thread David Johnston
-Original Message- From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Alexander Farber Sent: Thursday, December 29, 2011 3:01 PM Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Verifying a timestamp is null or in the past Thank you And

[GENERAL]

2011-12-29 Thread dhaval jaiswal
Might be discussed but not clear for the below query. In async. streaming replication do I need to run VACUUM & ANALYZE on both master & slave as to it is bit to bit replication. Bec, while querying on master getting below result, but slave's system table is not updated. select last_vacuum

[GENERAL] streaming replication vacuum

2011-12-29 Thread dhaval jaiswal
Might be discussed but not clear for the below query. In async. streaming replication do I need to run VACUUM & ANALYZE on both master & slave. Bec, while querying on master getting below result, but slave's system table is not updated. select last_vacuum, last_autovacuum, last_analyze, l