On Thu, May 24, 2012 at 2:40 AM, Edmund Horner wrote:
> On 24 May 2012 12:33, Bruce Momjian wrote:
>> I have applied the attached patch which should fix the problem. How
>> can we get Edmund a copy of a new binary for testing? Does he have to
>> wait for beta2?
>
> My uneducated guess is that
On Thu, May 24, 2012 at 03:42:25PM +0200, Magnus Hagander wrote:
> On Thu, May 24, 2012 at 2:40 AM, Edmund Horner wrote:
> > On 24 May 2012 12:33, Bruce Momjian wrote:
> >> I have applied the attached patch which should fix the problem. How
> >> can we get Edmund a copy of a new binary for test
The following bug has been logged on the website:
Bug reference: 6663
Logged by: Gilson Lasco
Email address: gilsonla...@yahoo.com
PostgreSQL version: 9.1.3
Operating system: Linux Ubuntu 12.04 x64
Description:
while PQconnectdb returns addresses below 2gb, PQfinish w
The following bug has been logged on the website:
Bug reference: 6664
Logged by: Karthik Ananth
Email address: karthik.jc...@gmail.com
PostgreSQL version: 9.0.7
Operating system: Freebsd 8.2, Freebsd 7.2
Description:
As per the documentation by default postgres serve
karthik.jc...@gmail.com writes:
> As per the documentation by default postgres server should run in
> foreground. I am referring to this link -
> http://www.postgresql.org/docs/9.0/static/server-start.html
> But what I have observed is, it is not happening and the command returns
> immediately. Be
Hi Tom,
You are right. That worked. I feel it is a documentation bug as with the
default settings, executing the provided command would not start the server
in foreground mode.
The default setting for silent_mode is on is what I have seen.
Regards
Karthik
On Thu, May 24, 2012 at 7:46 PM, Tom L
karthik ananth writes:
> Hi Tom,
> You are right. That worked. I feel it is a documentation bug as with the
> default settings, executing the provided command would not start the server
> in foreground mode.
> The default setting for silent_mode is on is what I have seen.
No, that has certainly
Jeff Frost writes:
> A few times today, we've seen postgresql 9.1.3 backends on Ubuntu 11.10 x86_64
> get stuck in 'startup' mode. By that I mean the set_ps_output mode. Postgres
> is installed via Martin Pitt's packages.
I took another look at your original report here, and noticed something
th
karthik ananth writes:
> The default postgres.conf created would have this setting set to "on". I
> used the freebsd port to install.
Hmm. That's certainly not the case in stock Postgres, so I suppose the
freebsd packager must be patching it for some reason. Perhaps the start
script he's using
On 05/24/12 12:21, Tom Lane wrote:
> Jeff Frost writes:
>> A few times today, we've seen postgresql 9.1.3 backends on Ubuntu 11.10
>> x86_64
>> get stuck in 'startup' mode. By that I mean the set_ps_output mode. Postgres
>> is installed via Martin Pitt's packages.
> I took another look at your o
Jeff Frost writes:
> On 05/24/12 12:21, Tom Lane wrote:
>> How big is pg_attribute normally in this database? I'm suspicious that
>> what triggered this is some major bloating of pg_attribute (and maybe
>> some of the other catalogs too).
> So, the current working system's pg_attribute looks lik
On May 24, 2012, at 3:13 PM, Tom Lane wrote:
> Jeff Frost writes:
>> On 05/24/12 12:21, Tom Lane wrote:
>
> Huh. A bit bigger, but not by that much. It doesn't seem like this
> would be enough to make seqscan performance fall off a cliff, as it
> apparently did. Unless maybe the slightly-blo
Jeff Frost writes:
> On May 24, 2012, at 3:13 PM, Tom Lane wrote:
>> Huh. A bit bigger, but not by that much. It doesn't seem like this
>> would be enough to make seqscan performance fall off a cliff, as it
>> apparently did. Unless maybe the slightly-bloated catalogs were just a
>> bit too lar
On May 24, 2012, at 3:35 PM, Tom Lane wrote:
> Jeff Frost writes:
>> On May 24, 2012, at 3:13 PM, Tom Lane wrote:
>>> Huh. A bit bigger, but not by that much. It doesn't seem like this
>>> would be enough to make seqscan performance fall off a cliff, as it
>>> apparently did. Unless maybe the
On 25 May 2012 01:59, Bruce Momjian wrote:
> On Thu, May 24, 2012 at 03:42:25PM +0200, Magnus Hagander wrote:
>> I've built a new one off git master + Bruce's patch. You can get it
>> from http://www.hagander.net/tmp/pg_upgrade.zip - please see if that
>> one works for you.
>
> Thanks, but thinkin
On 25 May 2012 11:48, Edmund Horner wrote:
> It still fails (when run in verbose mode):
Sorry, let me correct that to:
It still fails, regardless of verbose mode. And, in verbose mode, the
output is...
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
On Fri, May 25, 2012 at 11:48:53AM +1200, Edmund Horner wrote:
> It still fails (when run in verbose mode):
>
> Creating catalog dump
> ""c:\ehorner\pgsql\bin/pg_dumpall" --port 50432 --username "ehorner"
> --schema-only --binary-upgrade --verbose > "pg_upgrade_dump_all.sql"
> 2>> "pg_upgrade_
Hi, Robert.
$ psql --version
psql (PostgreSQL) 9.1.2
D J
On Tue, May 22, 2012 at 12:55 PM, Robert Haas wrote:
> On Sun, May 13, 2012 at 10:46 PM, Thangalin wrote:
> > Hi,
> >
> > REPLICATE
> >
> > 0. Create a new database (superdatabase)
> > 1. Create a new schema (superschema)
> > 2. Add the
18 matches
Mail list logo
