How about adding this patch to postgresql it will slove the problem?
On Sun, Jul 5, 2009 at 8:10 PM, Greg Stark wrote:
> On Sun, Jul 5, 2009 at 4:28 PM, Tom Lane wrote:
>> when i done dump->restore i
>>> have surprise,
>>> Column ordering was changed.
>>
>> This is not a bug, it's the intended beh
Steve Purcell writes:
> # su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
> PGCLUSTER=8.4/main pg_restore -d template1 -C"
>
> And the debian pg_wrapper script ends up selecting the 8.3 pg_dump binary in
> the first case. I'll have to figure out if there's even a way to execute
> the
After upgrading to 8.4 on Vista I see no progress on the shared memory
problem unfortunately.
I think it's even worse now (previously it happened mainly when OS
went to sleep & then was restored, now it's all the time).
My log looks like this.
-
On Mon, Jul 6, 2009 at 11:20 AM, wstrzalka wrote:
> After upgrading to 8.4 on Vista I see no progress on the shared memory
> problem unfortunately.
>
> I think it's even worse now (previously it happened mainly when OS
> went to sleep & then was restored, now it's all the time).
>
> My log looks li
On 2009-07-05, Steve Purcell wrote:
> Thanks for the quick reply, Tom. That makes sense, and yes, that does
> appear to be the problem.
>
> I thought that I *was* using the newer pg_dump, but I'm doing this on
> Debian:
>
> # su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
> PGCLU
No really a pattern.
I'm sure PG is installed in standard pure version everywhere.
No domains at all.
The rest is really custom (we are working remotely - each of us with
different hardware, OS, software, etc...).
Maybe the intel dual core has smth to do about it ?
Those are affected:
My
All of the machines are laptops. Maybe some power management stuff ?
> On Mon, Jul 6, 2009 at 11:20 AM, wstrzalka wrote:
>> After upgrading to 8.4 on Vista I see no progress on the shared memory
>> problem unfortunately.
>>
>> I think it's even worse now (previously it happened mainly when OS
2009/7/6 Wojciech Strzałka :
>
> No really a pattern.
> I'm sure PG is installed in standard pure version everywhere.
> No domains at all.
> The rest is really custom (we are working remotely - each of us with
> different hardware, OS, software, etc...).
> Maybe the intel dual core has smth t
Terrific, thanks for that. I'd figured out the first trick you
suggested, but the second is much clearer.
-Steve
On 6 Jul 2009, at 12:28, Dimitri Fontaine wrote:
Steve Purcell writes:
# su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
PGCLUSTER=8.4/main pg_restore -d template1
Wojciech Strza?ka wrote:
> All of the machines are laptops. Maybe some power management stuff ?
I experienced problems with the Standby mode (that was with pg8.2 and XPSP2).
But since this is a workstation I just stopped using the Standby mode.
I never looked into the log files but what happened
In my case standby mode only increases the frequency - problem occurs
also on clean machine - right after startup.
8.4 is totally unusable on my vista. I had to downgrade back to 8.3
I've just uninstalled antivirus & disabled windows firewall - no
effect.
The strange is that subsequent request
The uppercase 'TH' modifier is not working with HH12:
template1=# select to_char('3-MAY-2007 2:34'::timestamptz,'FMHHTH" HOUR
OF THE "FMDDTH" DAY WAS ILL-FATED'::text);
to_char
---
2nd HOUR OF THE 3RD DAY WAS ILL-FATED
(1 row)
Looking at the c
Heikki Linnakangas writes:
> Looking at the code, that looks like an oversight and the fix is trivial:
Yeah, I think you are right.
> But given that it has been like that at least back to 8.0 which is the
> oldest version I have installed right now: does anyone see a reason not
> to fix that?
+
> your theory is pretty much nonsense
...
> What I think is happening is that '(' is a sufficiently common value
that
> the planner thinks a seqscan is superior to an indexscan for it.
Your theory is also "pretty much nonsense" if you read the detailed
description I gave in my initial post, in whi
On Mon, Jul 6, 2009 at 5:40 PM, Peter Headland wrote:
> presence
> of a '(' character anywhere at all in the string literal triggers the
> problem. For example 'abc(def'.
Except according to that explain analyze 'abc(def' ran exactly the
speed as 'abc()def'.
This all seems much more likely to dep
As I said further down my previous e-mail, it looks as if the optimizer
is just fine, and the problem is simply a bug in the way pgAdmin III
parses and displays EXPLAIN ANALYZE output in its graphical view.
--
Peter Headland
Architect - e.Reports
Actuate Corporation
-Original Message-
F
Tom Lane wrote:
> Heikki Linnakangas writes:
> > Looking at the code, that looks like an oversight and the fix is trivial:
>
> Yeah, I think you are right.
>
> > But given that it has been like that at least back to 8.0 which is the
> > oldest version I have installed right now: does anyone see
On Mon, Jul 06, 2009 at 01:53:28PM -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Heikki Linnakangas writes:
> > > Looking at the code, that looks like an oversight and the fix is
> > > trivial:
> >
> > Yeah, I think you are right.
> >
> > > But given that it has been like that at least back
David Fetter wrote:
> On Mon, Jul 06, 2009 at 01:53:28PM -0400, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Heikki Linnakangas writes:
> > > > Looking at the code, that looks like an oversight and the fix is
> > > > trivial:
> > >
> > > Yeah, I think you are right.
> > >
> > > > But given tha
On Mon, Jul 6, 2009 at 7:20 PM, Bruce Momjian wrote:
> I feel like someone should take a flame-thrower to that file. ;-)
If you were half the man you used to be would you?
--
greg
http://mit.edu/~gsstark/resume.pdf
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make change
Greg Stark wrote:
> On Mon, Jul 6, 2009 at 7:20 PM, Bruce Momjian wrote:
> > I feel like someone should take a flame-thrower to that file. ?;-)
>
> If you were half the man you used to be would you?
I thought we had flame-throwed it a couple of of times, with overhauls,
but obviously we didn't do
On Mon, Jul 06, 2009 at 02:30:12PM -0400, Bruce Momjian wrote:
> Greg Stark wrote:
> > On Mon, Jul 6, 2009 at 7:20 PM, Bruce Momjian wrote:
> > > I feel like someone should take a flame-thrower to that file.
> > > ?;-)
> >
> > If you were half the man you used to be would you?
>
> I thought we ha
David Fetter writes:
> On Mon, Jul 6, 2009 at 7:20 PM, Bruce Momjian wrote:
>>> I feel like someone should take a flame-thrower to that file.
> Dunno about the file, but the whole question of date and time handling
> has been tricky and complicated for all of human history.
Yeah. I think about
David Fetter wrote:
> Dunno about the file, but the whole question of date and time handling
> has been tricky and complicated for all of human history.
Yeah, the rules on how to parse the pattern and how to use it to
interpret/format dates are indeed very complex. And this was a
particularly obsc
The following bug has been logged online:
Bug reference: 4903
Logged by: Oscar Miguel Amezcua Estrella
Email address: obel...@gmail.com
PostgreSQL version: 8.4
Operating system: Opensuse 11.1
Description:Sugestion a db modele like mysql workbrench
Details:
hiyas im
I don't suppose this explains anything but - why not to try (this is
DEBUG and has more details, but looks like some information are less detailed
than in
INFO log level ?? (ie. socket error code is missing):
2009-07-06 23:31:12 CEST DEBUG: 0: shmem_exit(0)
2009-07-06 23:31:12 CEST LOCATION
Wojciech Strzałka escribió:
>
> I don't suppose this explains anything but - why not to try (this is
> DEBUG and has more details, but looks like some information are less detailed
> than in
> INFO log level ?? (ie. socket error code is missing):
I suggest you add %p to log_line_prefix to differ
Hi!
There is a known Logoff/CreateProcess problem at MS:
http://support.microsoft.com/kb/960266/en-us
But even installing this hotfix didn't solve the problem.
Nobody out there with an idea?
Bye
Gerhard Leykam
Gerhard Leykam schrieb:
The following bug has been logged online:
Bug refere
Hello, Oscar.
First of all you shouldn't post such messages here since this is not a
bug for sure.
Take a look on MicroOLAP Database Designer for PostgreSQL at
http://microolap.com/products/database/postgresql-designer/
You will be surprised :)
You wrote:
OMAE> The following bug has been logge
The following bug has been logged online:
Bug reference: 4904
Logged by: ajay
Email address: ajaykumar.ga...@yahoo.com
PostgreSQL version: 8.3.7
Operating system: windows xp service pack2
Description:mapping between security ids and account name missing
Details:
hi,
30 matches
Mail list logo
