Re: [GENERAL] pg_dumpall behavior in 9.1beta1

2011-05-13 Thread Rajesh Kumar Mallah
oops! sorry for the noise it was an innocuous 'NOTICE' not ERROR as claimed. thanks for your time. regds mallah. On Fri, May 13, 2011 at 7:59 PM, Tom Lane wrote: > Rajesh Kumar Mallah writes: >> We migrated to 9.1beta1 from 9.0.x in our development environment. >> we shall report if any sign

Re: [GENERAL] pg_dump on Hot standby : clarification on how to

2011-05-13 Thread Dan Birken
What is your "max_standby_streaming_delay" set at? If your pg_dump takes longer than your "max_standby_streaming_delay" (which is likely since the default is 30s), you might get that error as well. This setting tells your standby how long it should wait to apply conflicting WAL files to finish a

Re: [GENERAL] Postgredac Dump

2011-05-13 Thread Bob Pawley
Hi Ray I finally got it to dump. I switched the argument so that the path is first and the file name is after the comma. I found this hint on a very useful site that shows a number of examples of PostgresDAC. http://www.keashsoft.com/postgrestutorial/4.html Bob -Original Message-

Re: [GENERAL] Postgredac Dump

2011-05-13 Thread Bob Pawley
The last log entry was two hours before I attempted to dump. Bob -Original Message- From: Raymond O'Donnell Sent: Friday, May 13, 2011 10:44 AM To: Bob Pawley Cc: raghu ram ; Postgresql Subject: Re: [GENERAL] Postgredac Dump On 13/05/2011 18:30, Bob Pawley wrote: Hi Raghu Thanks

Re: [GENERAL] simple update query too long

2011-05-13 Thread Merlin Moncure
On Fri, May 13, 2011 at 2:07 AM, F T wrote: > Thanks for your ideas. > > I have rerun my tests and I agree with Merlin, PostgreSQL is not adapted at > all to handle wide updates. > > Summary : > The table contains 2 millions rows. > > Test 1 : > UPDATE grille SET inter=0; -> It tooks 10 hours > >

Re: [GENERAL] simple update query too long

2011-05-13 Thread Isabella Ghiurea
Hi, I would suggest if you can try one of this options: 0- create a new index on " inter "column for grille table and in your WHERE clause try to limit the number of update rows instead of 2mills for one the whole transaction , something like :where inter > x and inter < y; 1- drop at least t

Re: [GENERAL] pg_dump on Hot standby : clarification on how to

2011-05-13 Thread bubba postgres
What I mean is if I do pg_dump on slave I get the " ERROR: canceling statement due to conflict with recovery". So I googled and tried the solution listed in the linked thread. I did a "start transaction" via psql on the master but I continued to get the error. Wondered if there was more to it than

Re: [GENERAL] Postgredac Dump

2011-05-13 Thread Raymond O'Donnell
On 13/05/2011 18:30, Bob Pawley wrote: Hi Raghu Thanks for the site. I am still having problems. The following downloads a file of 0 bytes. procedure TForm1.Button3Click(Sender: TObject); begin PSQLDump1.DumpToFile('E5R', 'C:\PDW\E5R'); end; (E5R is the database name.) The Dump component points t

Re: [GENERAL] Postgredac Dump

2011-05-13 Thread Bob Pawley
Hi Raghu Thanks for the site. I am still having problems. The following downloads a file of 0 bytes. procedure TForm1.Button3Click(Sender: TObject); begin PSQLDump1.DumpToFile('E5R', 'C:\PDW\E5R'); end; (E5R is the database name.) The Dump component points to a viable database. I

Re: [GENERAL] How to handle bogus nulls from ActiveRecord

2011-05-13 Thread James B. Byrne
On Fri, May 13, 2011 11:50, Dickson S. Guedes wrote: > > Well, fetching from database it came nil and when saved into, it was > trying to save a serialized object. From postgresql_adapter.rb [1] > you > can see that it returns the correct internal type based when field > type is datetime, but i c

[GENERAL] Migrating to a WAL-shipped replication cluster

2011-05-13 Thread Derrick Rice
Happy Friday, I'm migrating a set of data, about 16G of SQL-dump (-F plain), to a postgresql instance with WAL shipping backups. My plan is to do this in subsets of data, as there some work that has to be done with the dump before it is moved over. Let's assume 8 chunks ranging from 1G to 4G in

[GENERAL] Link error when use functions of PGtypes

2011-05-13 Thread Fanbin Meng
Hi: I installed PostgreSQL9.0 from EnterpriseDB with“one click installer” in windows 7 & 32bit. and use microsoft visual studio 2010 c++. I added the libpq.lib to the link property of the project, also included the lib folder and path. Successfully compiled .c and .cpp file after transfer .pg

Re: [GENERAL] Debug Contrib/cube code

2011-05-13 Thread Nick Raj
Hi, I am able to debug postgres by --enable-debug but breakpoint in cube is not working. Can you more elaborate on your second point? Even i also tried to change makefile of contrib/cube by -g(debug) but it gives error. Any idea is welcome. ps: sorry for late reply Thanks On Thu, May 12, 2011

Re: [GENERAL] How to handle bogus nulls from ActiveRecord

2011-05-13 Thread Dickson S. Guedes
2011/5/13 James B. Byrne : > Actually, it turn out that 'infinity' is supported in Ruby. > Apparently infinity can be represented by assigning the value > obtained by dividing a float by zero. > > $ irb > ruby-1.8.7-p334 :001 > infinity = 1.0/0 >  => Infinity > ruby-1.8.7-p334 :002 > ninfinity = -1

Re: [GENERAL] pg_dumpall behavior in 9.1beta1

2011-05-13 Thread Tom Lane
Rajesh Kumar Mallah writes: > We migrated to 9.1beta1 from 9.0.x in our development environment. > we shall report if any significant problems or issue arises out of this. > one small thing that we observed rite now regarding pg_dumpall output is that > the ALTER USER is referring to some db obj

Re: [GENERAL] How to handle bogus nulls from ActiveRecord

2011-05-13 Thread James B. Byrne
On Thu, May 12, 2011 20:30, Eric Hu wrote: > David suggested using a guesstimate default date along with > a boolean to indicate when you're using guesstimates. > I think this is a solid approach, but if the default > expected_by idea doesn't work for you, a boolean > would still make this a lot e

Re: [GENERAL] simple update query too long

2011-05-13 Thread Misa Simic
Hi, Would it be faster if you create Partial Index on inter field (btree) where inter > 0 and then UPDATE grille SET inter = 0 WHERE inter > 0 Kind Regards, Misa 2011/5/9 F T > Hi list > > I use PostgreSQL 8.4.4. (with Postgis 1.4) > > I have a simple update query that takes hours to run. >

[GENERAL] pg_dumpall behavior in 9.1beta1

2011-05-13 Thread Rajesh Kumar Mallah
Dear List , We migrated to 9.1beta1 from 9.0.x in our development environment. we shall report if any significant problems or issue arises out of this. one small thing that we observed rite now regarding pg_dumpall output is that the ALTER USER is referring to some db objects which are not creat

Re: [GENERAL] simple update query too long

2011-05-13 Thread Oleg Bartunov
On Fri, 13 May 2011, F T wrote: Thanks for your ideas. I have rerun my tests and I agree with Merlin, PostgreSQL is not adapted at all to handle wide updates. Summary : The table contains 2 millions rows. Test 1 : UPDATE grille SET inter=0; -> It tooks 10 hours Test 2 : I remove the spatial

Re: [GENERAL] simple update query too long

2011-05-13 Thread Pavel Stehule
2011/5/13 F T : > Thanks for your ideas. > > I have rerun my tests and I agree with Merlin, PostgreSQL is not adapted at > all to handle wide updates. > > Summary : > The table contains 2 millions rows. > > Test 1 : > UPDATE grille SET inter=0; -> It tooks 10 hours > > Test 2 : > I remove the spati

Re: [GENERAL] simple update query too long

2011-05-13 Thread F T
Thanks for your ideas. I have rerun my tests and I agree with Merlin, PostgreSQL is not adapted at all to handle wide updates. Summary : The table contains 2 millions rows. Test 1 : UPDATE grille SET inter=0; -> It tooks 10 hours Test 2 : I remove the spatial Gist index, and the constraints : I