The following bug has been logged on the website:
Bug reference: 7594
Logged by: Reinhard Max
Email address: m...@suse.de
PostgreSQL version: 9.1.6
Operating system: openSUSE
Description:
Is it intentional, that concurrent GRANT statements for the same database
may
On Fri, 21 Sep 2012 at 14:17, Tom Lane wrote:
All of the use-cases I've thought of for wanting to capture stderr
output for it amount to debugging of some form or other, so it's
probably good enough for that to only work in the first logger
incarnation after database start --- but Reinhard is
On Thu, 20 Sep 2012 at 11:06, Tom Lane wrote:
(I assume you mean pg_ctl not pg_init?)
Yes, sorry for the confusion.
Well, I would have no objection to changing pg_ctl so that it
redirects the postmaster's stdout/stderr when a -l switch is given
(actually, I thought it did that already...).
On Thu, 20 Sep 2012 at 10:31, Heikki Linnakangas wrote:
I believe Tom is referring to the removal of silent_mode in 9.2, see
http://archives.postgresql.org/pgsql-general/2011-06/msg00796.php
and
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02156.php.
"We removed logic associated w
On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
reinh...@m4x.de writes:
When initially starting up, syslogger keeps stdout and stderr open
instead of closing them and reopening them from /dev/null for
proper daemonisation.
How exactly could it "close and reopen" them without losing their
ide
The following bug has been logged on the website:
Bug reference: 7561
Logged by: Reinhard Max
Email address: m...@suse.de
PostgreSQL version: 9.1.5
Operating system: openSUSE
Description:
When initially starting up, syslogger keeps stdout and stderr open instead
of
The following bug has been logged on the website:
Bug reference: 7548
Logged by: Reinhard Max
Email address: m...@suse.de
PostgreSQL version: 9.1.5
Operating system: openSUSE
Description:
It looks like the attempt to remove pg_upgrade's dependency on pg_config
The following bug has been logged on the website:
Bug reference: 6386
Logged by: Max Kunz
Email address: max.k...@atip.de
PostgreSQL version: 9.0.0
Operating system: CentOs
Description:
Hello,
i've got a Problem during PITR.
The Systems stops always with
The following bug has been logged online:
Bug reference: 6229
Logged by: Max Kunz
Email address: ad...@m4ximus.de
PostgreSQL version: 8.1.3
Operating system: Suse
Description:Postgresql crashes after: LOG: statistics buffer is full
Details:
Hello,
i have detected
s?
>
> Hmm, I'm not sure. I'm not sure if that's sufficient and that it doesn't
> add any holes, but we can check that.
> At least I think on set default
> triggers we'd need to do something with the check performed from inside
> the trigger.
What's wro
Stephan Szabo wrote:
> On Thu, 17 May 2007, Tom Lane wrote:
>
>> Max Khon <[EMAIL PROTECTED]> writes:
>>> "delete from foo" fails:
>>> ERROR: update or delete on table "bar" violates foreign key constraint
>>> "foobar_fk0&q
> Except that SQL92 at least does seem to say in 11.8 that "All rows that
> are marked for deletion are effectively deleted at the end of the
> SQL-statement, prior to the checking of any integrity constraints." I
> think that likely makes our behavior wrong, but I'm not r
able "foobar"
SQL state: 23503
Detail: Key (bar_id)=(1) is still referenced from table "foobar".
Context: SQL statement "DELETE FROM ONLY "public"."bar" WHERE "foo_id" = $1"
PostgreSQL version: any (I tested on 8.2.4 for Win32 and 8.1.3 fo
The following bug has been logged online:
Bug reference: 2864
Logged by: max kuhar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: windows xp sp2
Description:can't instal postgresql
Details:
when installer gets to setting up the ac
Tom Lane a écrit :
"Jean-Max Reymond" <[EMAIL PROTECTED]> writes:
So, spi_exec_query allocates memory but this memory is never released until
the end of the stored procedure.
Ah, found it.
OK, it solves my problem.
great job :-)
thanks a lot Tom
begin:vcard
fn:
Jean-Max Reymond a écrit :
Jean-Max Reymond a écrit :
The following bug has been logged online:
Bug reference: 1739
Logged by: Jean-Max Reymond
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux Ubuntu
Description:memory leak in pl
Jean-Max Reymond a écrit :
The following bug has been logged online:
Bug reference: 1739
Logged by: Jean-Max Reymond
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux Ubuntu
Description:memory leak in pl/perl with spi_exec_query
The following bug has been logged online:
Bug reference: 1739
Logged by: Jean-Max Reymond
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux Ubuntu
Description:memory leak in pl/perl with spi_exec_query
Details:
whith this code 1
Ao ser executado, após a escolha do idioma, ocorre a seguinte mensagem de erro:
Failed to process: 2! e aborta a instalação.
Grato
Max Marcell
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
buffer = temp_buffer;
Regards,
Max Kellermann
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Wed, 6 Aug 2003 at 18:02, Tom Lane wrote:
> Mahlon Stacy <[EMAIL PROTECTED]> writes:
> > Newer versions of TCL implement ByteArray objects which are
> > the best fit for Postgresql Large Object functions.
>
> How newer is "newer"? That is, what compatibility problems might we
> create if we ma
ore
parameters, so that databases can be addressed by a nickname. I think
of something like
--- snip ---
foo password=foopass
bar hostname=foo.bar.com dbname=foodb user=max password=xyz
--- snap ---
So even the remote "bar" database could be accessed by a simple
$ psql bar
If there is sti
On 4 Sep 2002 at 12:48, Rod Taylor wrote:
> This item:
> Add file to hold passwords using PGPASSWORDFILE environment variable
>
> Has been completed, and will be a part of the 7.3 release.
Is there a default file name like ~/.pgpassword so that this feature
can be used without setting yet anothe
On Tue, 18 Jun 2002 at 09:28, David M. Kaplan wrote:
> Thanks, that did fix that problem. Now I have another one. The line:
>
> hostall192.168.1.2255.255.255.128password
>
> matches all ip addresses of the form 192.168.1.x. If I change the mask
> to 255.255.255.255 it no longer
Hi,
On Mon, 17 Jun 2002 at 20:47, David M. Kaplan wrote:
> host all 127.0.0.1 0.0.0.0identsameuser
If you want this entry to match only the loopback device, the mask has
to be 255.255.255.255 instead of 0.0.0.0. A mask of 0.0.0.0 causes
*all* IP addresses to match this
Hi,
On Tue, 9 Apr 2002 at 19:43, Thomas Lockhart wrote:
> I don't think that our code checks explicitly for a "-1" return, since
> the range is checked just before the call, but it would probably be a
> good idea if it did
Indeed.
As I noticd yesterday, glibc's mktime() has in the current snap
Hi,
On Fri, 1 Mar 2002 at 09:37, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
>
> > I'll tell my colleague (it's his test database, after all) that he
> > should take more realistic test data before complaining about bad
> > performance...
&
s indexscan seem to be many fewer than
> the number of rows in the table. What are the ranges of the id
> values in tables foo and bar? I'm wondering if the merge could have
> stopped far short of the end of the foo table; if so, *that* is the
> effect that we are failing to model a
ith just
> fabs(indexCorrelation) to see if the results are better. Also, if you
> cared to step through the code with a debugger or add some printout
> statements, we could learn what the min and max costs are that it's
> interpolating between; that'd be interesting to know as
On Thu, 28 Feb 2002 at 09:51, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
> > I've just found a case where forcing indexscans results in much higher
> > speed.
>
> > -> Index Scan using foo_pkey on foo
> >
s results in much higher
speed. On the the 35 rows table mentioned in my other post after a
"VACUUM FULL ANALYZE":
max=# set enable_seqscan to false;
max=# EXPLAIN analyze
SELECT count(foo.id) FROM foo, bar
WHERE foo.id = bar.ref2foo;
Aggregate (cost
Hi,
I am not sure whether the behaviour described below is to be expected
or to be considered as a bug, but I bet you can tell me ;)
I have a table defined as follows:
CREATE TABLE "foo" (
"id" int NOT NULL,
"name" character varying(256) NOT NULL,
"street" character vary
Hi,
as of 7.2b5 'libpq++.h' includes 'libpq++/pgconnection.h' which in
turn tries to include 'postgres_fe.h' which can't be found because it
has bee moved to the 'internal' subdirectory.
Are applications now required to supply -I/usr/include/pgsql/internal
in addition to -I/usr/include/pgsql or
Hi.
Are you sure it's for me ?
In the bugreport said about mysql2pgsql, however I'm the author of my2pg.pl.
Both tools are distributed with Postgres source distribution.
Please confirm that's really for me.
Thanks.
Max Rudensky.
On Wed, 10 Oct 2001 15:45:22 -0400 (EDT)
Bruce
Hi Bruce,
On Wed, 5 Sep 2001, Bruce Momjian wrote:
> I have a patch here that handles all the TCL/UTF issues.
> Would you let me know if it is OK?
I think, it isn't really a clean fix. It only works, if your
database's encoding and Tcl's system encoding are identical. If the
database uses a dif
On Fri, 20 Jul 2001, Peter Eisentraut wrote:
> Reinhard Max writes:
>
> > OK, I'll pack the new stuff inside #ifdef TCL_UTF8 and define that if
> > the Tcl version is 8.1 or greater.
>
> No, please add a configure check for Tcl_UtfToExternalDString or
> some other
On Wed, 18 Jul 2001, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
> > On Wed, 18 Jul 2001, Bruce Momjian wrote:
> >> Do you have any idea how this will work with earlier TCL versions?
>
> > It won't. If pgtcl is supposed to still be able to
On Wed, 18 Jul 2001, Tom Lane wrote:
> Reinhard Max <[EMAIL PROTECTED]> writes:
> > On Wed, 18 Jul 2001, Bruce Momjian wrote:
> >> Do you have any idea how this will work with earlier TCL versions?
>
> > It won't. If pgtcl is supposed to still be able to
ng added to TCL?
According to Tcl's changelog files, it was added in 1997 for Tcl 8.1
wich was released in 1999.
cu
Reinhard Max
Maintainer of the Tcl/Tk and PostgreSQL packages for SuSE Linux
---(end of broadcast)---
TIP 3: if posting
On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote:
> Installing Postgress on a Red Hat 7.0 Server, some regression test
> failed (see below). How can i fix this failed queries?
I had similar results here at SuSE. They came from a locale bug in
glibc-2.2 . As a workaround, try to unset LANG or set it t
Hi,
On Wed, 14 Feb 2001 [EMAIL PROTECTED] wrote:
> fmatheus ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> NOTICE: pg_setlocale()
>
> Long Description
> Im a Debian user of postgresql version 7.0.3-4.
> libc6 and loca
x27;aaa',null);
--
ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ,
îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ
(8312) 30-19-05, 34-00-02, 30-09-73
With best regards, Max Vaschenko,
Nizhny Novgorod Information Networks.
Tom Lane wrote:
>
> Max Vaschenko <[EMAIL PROTECTED]> writes:
> > After some (2-3 weeks) time both postmaster and all (every) backends take
> > about 60mb memory.
>
> Okay, then it is a postmaster leak. The backends are started by fork
> from the postmaster
Tom Lane wrote:
>
> Max Vaschenko <[EMAIL PROTECTED]> writes:
> > I have a RedHat Linux 6.2 (kernel 2.2.18pre1 SMP) on Intel platform.
> > Postgres-7.0.3-2 (RPM).
> > It grows. Initially about 5mb it grows to 60-70 mb after 2-3 weeks.
>
> Is this th
chroot (via hardlinked socket /tmp/.s.PGSQL.5432)
Some times ago i upgraded it from 7.0.2 version, that grew too.
--
ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ,
îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ
(8312) 30-19-05, 34-00-02, 30-09-73
With best regards, Max Vaschenko,
Nizhny Novgorod Information Networks.
Postgres-7.0.3-2
RedHat-6.2
SELECT int8(5*27.81*100);
13904
SELECT int4(5*27.81*100);
13905
SELECT int8(27.81*100*5);
13905
--
ó Õ×ÁÖÅÎÉÅÍ, ÷ÁÝÅÎËÏ íÁËÓÉÍ,
îÉÖÅÇÏÒÏÄÓËÉÅ ÉÎÆÏÒÍÁÃÉÏÎÎÙÅ ÓÅÔÉ
(8312) 30-19-05, 34-00-02, 30-09-73
With best regards, Max Vaschenko,
Nizhny
n-progress state
FATAL 1: The system is shutting down
Anyone have advice as to how to remedy this from my side or is this a postgres
problem?
Thanks in advance!
--
Max Pyziur BRAMA - Gateway Ukraine
[EMAIL
Hi,
On Mon, 30 Oct 2000, Thomas Lockhart wrote:
> > Just to let you know it looks like ver 7.0 does not run on SuSE7.0 SMP
> > Kernel. Has this been fixed on 7.02 at all?
>
> As Peter asked, we need more info to help you. But fwiw, I've been
> running on SMP linux for several years with no probl
On Mon, 11 Sep 2000, Lamar Owen wrote:
> Max Pyziur wrote:
> > I dropped my databases, uninstalled the 7.0.2-2 rpms and installed 6.5.3 rpms on
> > my development RH6.2 Linux 2.2.14-5.0 system and I still get the anomalous query
> > result on that box.
>
> This is
Tom Lane wrote:
>
> Max Pyziur <[EMAIL PROTECTED]> writes:
> >> That's pretty bizarre (not to say difficult to believe). What LOCALE
> >> setting are you running the postmaster in?
>
> > On none of the installations - the two 6.5.x and the 7.0.2-2 o
Tom Lane wrote:
>
> Max Pyziur <[EMAIL PROTECTED]> writes:
> > I've come across what I consider an odd sorting anomaly in 7.0.2-2 where running
> > the following query:
> > select headline from headlines where headline like 'Alb%' order by 1 ;
>
s2 | deckard | SQL_ASCII
headlines3 | deckard | LATIN1
to see if the results are different. Each of the encodings produces the same
anomalous results.
Any help in this regard as well as resolving it would be appreciated. Details
of systems and schema are append
src/backend/libpq/pqcomm.c as workarround for the PostgreSQL RPMs for
SuSE Linux which I am currently working on. The patch (hack) doing
this is also included.
Regards,
Reinhard Max
--
If you put garbage in a computer nothing comes out but garbage.
But this garbage, having passed throug
53 matches
Mail list logo
