On 07/05/2012 09:06 PM, Gary Haran wrote:
I installed it using an hstore.sql file that comes with the home brew
(https://github.com/mxcl/homebrew/) version of postgresql on OS X.
Maybe we missed a step or something in the whole installation process.
We most likely upgraded our pg version at s
On Thu, Jul 05, 2012 at 12:21:58AM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> >>> address the points I made about reproducing the previous state in cases
> >>> where the admin removed the language or changed its permissions.
>
> >> Well, it still does the create extension in binary mode lik
On Thu, Jul 5, 2012 at 1:56 AM, Craig Ringer wrote:
> On 07/05/2012 02:05 AM, gary.ha...@gmail.com wrote:
>>
>> development=# create extension hstore;
>> ERROR: type "hstore" already exists
>
> First, thanks for the info in the report.
>
> At a guess, it has the hstore data type in it from before
I installed it using an hstore.sql file that comes with the home brew (
https://github.com/mxcl/homebrew/) version of postgresql on OS X. Maybe we
missed a step or something in the whole installation process.
We most likely upgraded our pg version at some point (we try to stay with
the times).
T
On 07/05/2012 10:18 PM, Jaime Casanova wrote:
On Thu, Jul 5, 2012 at 1:56 AM, Craig Ringer wrote:
On 07/05/2012 02:05 AM, gary.ha...@gmail.com wrote:
development=# create extension hstore;
ERROR: type "hstore" already exists
First, thanks for the info in the report.
At a guess, it has the h
Hello,
I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
Although the upgrade completed successfully, vacuumdb --all --analyze-only
gives an error. I tried upgrading two binary backups of the same production
database from different days, and both returned the exact same error
On 07/05/2012 11:20 PM, Payal Singh wrote:
Hello,
I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
Although the upgrade completed successfully, vacuumdb --all
--analyze-only gives an error. I tried upgrading two binary backups of
the same production database from differen
Josh Kupershmidt writes:
> On Tue, Jul 3, 2012 at 11:41 PM, Tom Lane wrote:
>> The get_parent_directory() call reduces "foo.sql" to an empty string,
>> which seems a tad bogus --- wouldn't "." be better? But in any case,
>> join_path_components() thinks it can process a "../" prefix of the
>> ta
I wrote:
> On reflection I think that what we need to do is fix it so that it only
> strips "../" from the tail string when there is a directory name
> available to be stripped from the head string. Otherwise just stop
> trimming.
Actually, there is a much simpler fix: don't let it strip ".." at
Thank you. That worked.
Regards
Payal
On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
> On 07/05/2012 11:20 PM, Payal Singh wrote:
>
> Hello,
>
> I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
> Although the upgrade completed successfully, vacuumdb --all --analyze
Payal Singh writes:
> On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
>> If you start 9.1 on a copy of the backup then cleanly stop it again, does
>> pg_upgrade then run?
> Thank you. That worked.
ISTM that pg_upgrade should check that the old cluster was shut down
cleanly, ie pg_control h
The following bug has been logged on the website:
Bug reference: 6720
Logged by: balaji
Email address: balaj...@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Windows Xp
Description:
Hi,
Am using version 1.14.1 it often disconnecting with some er
The following bug has been logged on the website:
Bug reference: 6719
Logged by: BLove
Email address: blove...@hotmail.com
PostgreSQL version: 9.1.3
Operating system: Centos 5
Description:
After doing an equality search on an indexed field, PG is doing a filter on
the
blove...@hotmail.com writes:
> After doing an equality search on an indexed field, PG is doing a filter on
> the same value using a regex. That appears to be a useless operation that
> will only consume cpu cycles.
Getting rid of the filter expression isn't really worth the trouble.
If we had do
On 07/06/2012 03:57 AM, balaj...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 6720
Logged by: balaji
Email address: balaj...@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Windows Xp
Description:
Error is PGADMIN 111
On Thu, Jul 05, 2012 at 06:28:31PM -0400, Tom Lane wrote:
> Payal Singh writes:
> > On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
> >> If you start 9.1 on a copy of the backup then cleanly stop it again, does
> >> pg_upgrade then run?
>
> > Thank you. That worked.
>
> ISTM that pg_upgrad
On 07/06/2012 12:19 PM, Balaji A wrote:
Thanks for replying and PFA screenshot and let me know if you need
more information on this.
Please re-read my reply, which explained to you what more information
would be needed and included a link to where you should follow this up.
I will repeat
17 matches
Mail list logo
