On Mon, Mar 7, 2011 at 5:20 PM, SandraA wrote:
> I am also having this problem. I used the One-Click installer provided by
> EnterpriseDB to install PostgreSQL 9.0.3. Is there a fix for the bug?
There is a fix in QA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
Enterprise
Em 07-03-2011 16:53, Owen Jacobson escreveu:
psql:repro.sql:2: ERROR: must be member of role "commented_role" to
comment upon it
This isn't a bug; let say it is a limitation (and a documented one [1]).
Unfortunately only the role, superuser or its members can add/drop comments.
[1] http://w
On Tue, Mar 8, 2011 at 1:32 AM, Jacob Lee wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5919
> Logged by: Jacob Lee
> Email address: jacobswel...@yahoo.com
> PostgreSQL version: 9.0.3
> Operating system: windows XP
> Description: released zippe
On Tue, Mar 8, 2011 at 12:49, Matyas Novak wrote:
> Bug reference: 5920
>
> create or replace function f2 () returns void volatile language sql as
> $$
> select f1(tmp) from (values ('aa'), ('bb')) _tmp(tmp);
> $$;
> select f2();
>
> As a result, only one row appears in table a, although two
The following bug has been logged online:
Bug reference: 5920
Logged by: Matyas Novak
Email address: lo...@centrum.cz
PostgreSQL version: 9.0.1
Operating system: linux
Description:SQL function are probably "overoptimized"
Details:
create table a(a integer);
create o
Thanks for that, I will do that. Sorry for the inconvenience it made.
- Original Message -
From: "Kevin Grittner"
To: pgsql-bugs@postgresql.org, "Allan Registos"
Sent: Tuesday, March 8, 2011 12:03:19 AM
Subject: Re: [BUGS] BUG #5916: PGAdmin crash
"Allan Registos" wrote:
> When
The following bug has been logged online:
Bug reference: 5919
Logged by: Jacob Lee
Email address: jacobswel...@yahoo.com
PostgreSQL version: 9.0.3
Operating system: windows XP
Description:released zipped files have problem
Details:
the oneclick installer version has
The following bug has been logged online:
Bug reference: 5918
Logged by: YAMAMOTO Takashi
Email address: y...@mwd.biglobe.ne.jp
PostgreSQL version: 9.1devel
Operating system: NetBSD
Description:SummarizeOldestCommittedSxact assertion failure
Details:
running 05d93c3
On 08/03/11 13:03, Mark Kirkwood wrote:
On 08/03/11 12:55, Mark Kirkwood wrote:
On 23/02/11 10:18, Mark Kirkwood wrote:
On 23/02/11 00:26, Greg Stark wrote:
It's also possible there's a bug of course. If someone was using that
buffer and somehow failed to notify the vacuum that they were done
On Mon, Mar 7, 2011 at 11:55 PM, Mark Kirkwood
wrote:
> stuff | 23957 | 2011-03-08 06:02:02.659159+13 | VACUUM ANALYZE;
>
For what it's worth VACUUM ANALYZE does have to take an additional
lock to update the statistics. It should rarely cause any problems but
it is a possibility.
When you d
On 08/03/11 12:55, Mark Kirkwood wrote:
On 23/02/11 10:18, Mark Kirkwood wrote:
On 23/02/11 00:26, Greg Stark wrote:
It's also possible there's a bug of course. If someone was using that
buffer and somehow failed to notify the vacuum that they were done it
would wait for a very long time (fore
On 23/02/11 10:18, Mark Kirkwood wrote:
On 23/02/11 00:26, Greg Stark wrote:
It's also possible there's a bug of course. If someone was using that
buffer and somehow failed to notify the vacuum that they were done it
would wait for a very long time (forever?). However if vacuum
eventually conti
Salut,
I'm making use of database-side comments to document the oddities and
intended uses for various database symbols. While this is mostly going
well, it's falling down a bit for documenting role objects. For the
record, I'm running the EnterpriseDB Postgres 9.0.3 package on OS X
10.6 as well a
I am also having this problem. I used the One-Click installer provided by
EnterpriseDB to install PostgreSQL 9.0.3. Is there a fix for the bug?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-5899-Memory-corruption-when-running-psql-tp3398967p3412773.html
Sent from
=?ISO-8859-15?Q?Torsten_Z=FChlsdorff?= writes:
> Now for the Problem: There is a problem with the translation of the
> english word "March" to the german "März". Instead of "März" i get
> "MäRz" (with uppercase "r").
> You can reproduce it as follow:
> # SET lc_time = "de_DE.UTF-8";
> # SELECT
On Mon, Mar 7, 2011 at 9:15 AM, Jakub Ouhrabka
wrote:
> for the archives: the root cause is locale. Both linux/debian servers were
> set to the same locale (cs_CZ.UTF-8) but there is slightly different
> definition of this locale on those systems - once numbers are before letters
> and another tim
"Allan Registos" wrote:
> When I press the SQL query, the whole pgadmin will close.
> Although, it works previously.
You might have a better chance of getting the attention of the right
people if you post to the pgadmin-support list. Even then, you
probably need to provide more information fo
I wrote:
> So yeah, something is pretty hosed here, but I don't think it's
> pg_stat_reset's fault ...
Oh, I see the problem: pgstat_recv_tabstat isn't bothering to initialize
those fields in a new entry.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@
Itagaki Takahiro writes:
> Some of pg_stat_all_tables.vacuum_count, autovacuum_count, analyze_count
> and autoanalyze_count will be filled with garbages after pg_stat_reset().
> Not all of the tables, but some of tables had corrupted counters.
> It looks we access freed memory. 9187201950435737471
Hi,
for the archives: the root cause is locale. Both linux/debian servers
were set to the same locale (cs_CZ.UTF-8) but there is slightly
different definition of this locale on those systems - once numbers are
before letters and another time numbers are after letters. Then the
index appears t
Some of pg_stat_all_tables.vacuum_count, autovacuum_count, analyze_count
and autoanalyze_count will be filled with garbages after pg_stat_reset().
Not all of the tables, but some of tables had corrupted counters.
It looks we access freed memory. 9187201950435737471 is 7F7F7F7F7F7F7F7F
filled by CLO
21 matches
Mail list logo
