The following bug has been logged online:
Bug reference: 4191
Logged by: Martin Saschek
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.7; 8.3.1
Operating system: Windows XP
Description:Include hint for Windows-like locals in documentation
Details:
include
The following bug has been logged online:
Bug reference: 4206
Logged by: Martin Drescher
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Windows XP SP2
Description:function xpath gives wrong results
Details:
To demonstrate I use the
key btree (id),
qmail_account_email_idx unique btree (username, "domain"),
qmail_account_contractid_idx btree (contractid),
qmail_account_username_idx btree (username)
Foreign Key constraints: $2 FOREIGN KEY ("domain") REFERENCES "zone"(name)
27;', NEW.domain;
SELECT INTO rec3 NEW.home || ''/'' ||
btrim(NEW.domain,'' '')::varchar || ''/'' ||
NEW.username AS home;
NEW.home := rec3.home;
END IF;
rying to reindex the index
> on zone(name).
I reindexed it several times. I didn't help.
Regards, Martin
- --
Martin Edlman
Fortech s.r.o, Litomysl
Public PGP key: http://edas.visaci.cz/#keys
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/WDSUoFlEKJy9loQRAsl/AJ4gYQ
l);
CREATE UNIQUE INDEX qmail_account_email_idx ON qmail_account (username,domain);
CREATE TABLE qmail_dot (
id SERIAL,
username varchar(50),
domain varchar(100) not null REFERENCES zone (name) ON UPDATE
CASCADE,
extension varchar(64),
dotqmail tex
On Mon, 3 Nov 2003, Tom Lane wrote:
> Martin Edlman <[EMAIL PROTECTED]> writes:
> > [ unstable index behavior ]
>
> I'm wondering about hardware problems --- how sure are you that you
> don't have flaky RAM or a bad disk drive?
I'll check this, the RAID co
So I expected that cs_CZ will be used in this case. :-( GRr.
Ok now it's working, thank you all who helped.
Martin
> Tomas Szepe <[EMAIL PROTECTED]> writes:
> > Martin, you can probably rule out the cs_CZ (LATIN2) locale as the cause
> > of your prob
x27;ve correctly identified the problem.
> However, it seems possible that part of the issue is misbehavior if
> the various LC_xxx settings aren't all alike --- could you dig further
> and try to isolate it?
I set ALL LC_xxx variables to cs_CZ in postgres.conf but it didn't help.
Only
.
Btw. setBinaryStream() should really throw an SQLException, if
in can not read as many bytes as expected from the InputStream.
Otherwise the application might silently loss data.
Regards
Martin
--
Martin Holz <[EMAIL PROTECTED]>
Softwareentwicklung / Vernetztes Studium - Chem
h fixes this by just ignoring -E when -P is not
given. The patch should work against your current CVS; it is already
included in the Debian package CVS.
Thanks and have a nice day!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED] [EMAIL PROTECT
On Friday 09 January 2004 09:46, Kris Jurka wrote:
> On Wed, 7 Jan 2004, Martin Holz wrote:
> > Hello,
> >
> > org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> > in postgresql 7.4.1 wrongly assumes, that
> > java.io.InputStream.read(byte[] b,int offs
On Friday 09 January 2004 09:46, Kris Jurka wrote:
> On Wed, 7 Jan 2004, Martin Holz wrote:
> > Hello,
> >
> > org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> > in postgresql 7.4.1 wrongly assumes, that
> > java.io.InputStream.read(byte[] b,int offs
here are two options
a) Throw a exception
b) Silently send all bytes, that are available.
I don't really understand what the length argument is good for
and think, that this is a design flaw made by Sun. I would prefer
a), but I am not sure here.
Martin
--
M
Kris Jurka <[EMAIL PROTECTED]> writes:
> On Wed, 7 Jan 2004, Martin Holz wrote:
>
> > Hello,
> >
> > org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
> > in postgresql 7.4.1 wrongly assumes, that
> > java.io.InputStream.read(byte[] b,int
us as to whether there
is actually a way to do it. Thanks for your patience.
regards,
martin
--
-------
Martin @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS:
(nullfd, 1);
dup2(nullfd, 2);
if (nullfd != 0 && nullfd != 1 && nullfd != 2)
close(nullfd);
(taken from syslog-ng which does it properly).
Can you do that in the next release?
Thanks in advance and have a nice day!
Martin
- Forwarded message from [EMAIL
ql/peer-to-ident: true
postgresql/missing_conf: true
* postgresql/purge_data_too: false
* postgresql/settings/encoding: UNICODE
* postgresql/settings/date_style: ISO
- End forwarded message -
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED]
Hi!
On 2004-05-12 1:31 +0200, Peter Eisentraut wrote:
> Martin Pitt wrote:
> > A week ago we at Debian received the bug report below: due to a
> > buffer overflow in psqlodbc it is possible to crash (and possibly
> > exploit) apache. I already sent this mail to the psqlo
here who can help with this?
I can reliably reproduce the error (using the small attached php4
script), but I do not know anything about the psqlodbc internals. I
would be glad if someone could assist me with that.
Thanks in advance and have a nice day!
Martin
[1] http://archives.postgresql.org
doing this is far beyond the scope of a
security patch (especially for Debian stable).
One question: which mailing list is the better place to discuss this?
-odbc or -bugs?
Thanks and have a nice day!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED]
Hi PostgreSQL hackers!
We recently got the Debian bug report below. Does anybody have an idea about that?
Thanks and have a nice day!
Martin
- Forwarded message from Peter Schueller <[EMAIL PROTECTED]> -
Subject: Bug#249036: postgresql: zero bytes cannot be entered in
!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.piware.de http://www.debian.org
diff -ruN postgresql-7.4.2-old/src/backend/storage/file/fd.c
postgresql-7.4.2/src/backend/storage/file/fd.c
--- postgresql
Hi!
On 2004-05-17 8:37 -0400, Bruce Momjian wrote:
> The issue is that bytea needs double-backslashes because single
> backslashes are processed by the parser into strings:
Indeed. Thank you for this!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PRO
Hi again!
Sorry for crossposting, but I sent the initial post also to -bugs,
because I did not get an answer on -odbc.
On 2004-05-11 12:03 +0200, Martin Pitt wrote:
> I noticed Apache segfaulting when I feed a simple form with long inputs:
>
> [Tue May 4 11:32:10 2004] [notice]
Hi PostgreSQL developers!
Does anybody happen to use Postgresql with winbind authentication? We
got the bug report below where this seems to crash.
Is this problem known?
Thanks and have a nice day!
Martin
- Forwarded message from Cory Dodt <[EMAIL PROTECTED]> -
Subject: Bug#
.
Thank you for this patch. I applied it and prepared an inofficial
package for the original submitter to test. I hoped to get a quick
answer from him, but up to now I didn't.
I will report back when I have any news.
Have a nice day!
Martin
--
Martin Pitt Debian GNU/Linux
the command line, as user postgres and got, instead:
98e3 ed40 9101 e340
These garbage strings are repeatable.
In either case, I did get the seg fault.
Does that say anything to anybody?
Thanks and have a nice day!
Martin
--
Martin Pit
e. converted it to hex (I quoted this part of his
message) to avoid problems with different encodings and mail filters.
For your convenience I wrote these hex sequences into two files
'token1' and 'token2' and tar.gz'ed them.
Thanks in advance and have a nice day!
Marti
d the whole source tree for an invocation of
next_token[_expand] and found nothing. Where the heck this is called
from? Looking at the stacktrace it seems to be kind of a callback from
libnss_wins, but somewhere this must be set!?
So who calls next_token and who sets the file, buffer and bufsz
p
Hi PostgreSQL developers!
Recently we got the following bug report about VACUUM FULL. Can
anybody comment on this?
If you have questions concerning the submitter's configuration, can
you please ask him directly? ([EMAIL PROTECTED])
Thanks in advance and have a nice day!
Martin
- Forw
not documented and the daemon is able to abort queries in
> this state.
>
> It makes systems unusable by stuck server processes which aren't
> abortable without admin intervention.
>
> Bastian
Thanks and have a nice day,
Martin
--
Martin Pitt
Hi Tom!
On 2004-06-23 11:09 -0400, Tom Lane wrote:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > Recently we got the following bug report about VACUUM FULL. Can
> > anybody comment on this?
>
> This was reported to the PG lists already. We asked for a test case
>
es.
This behaviour seems to confuse PostgreSQL autotoc.
Does this behaviour serve any purpose or it is an error?
Thanks and have a nice day!
Martin
- Forwarded message from Bastian Blank <[EMAIL PROTECTED]> -
Date: Sat, 29 May 2004 17:17:42 +0200
From: Bastian Blank <[EMAIL PRO
identifier is safe or not... so be safe not sorry.
This makes sense, thank you. I reassigned this bug to
postgresql-autodoc. Just ignoring the quotes cannot be that
difficult...
Thanks and have a nice day!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTE
t the solution below:
-
The binaries must be linked with pthread (-lpthread).
Regards,
Martin
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
all possible:
--
> ./configure --prefix=/opt/postgresql-800beta1 --enable-thread-safety
> make
> make check
make check gives me two errors, see attached diffs file.
Martin
*** ./expected/float4.out Fri Mar 12 01:2
num, &endptr);
+
+ if (endptr != num && endptr[-1] == 0)
+ endptr--;
+
/* did we not see anything that looks like a double? */
if (endptr == num || errno != 0)
Regards,
Martin Muenstermann
---(end of broadcast)---
TIP 8: explain analyze is your friend
, but also (or instead?) the linker flag
"-lpthread".
Maybe the case of a shared library using pthreads is not handled
correctly in the m4 macro?
Regards,
Martin
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
endptr. I seem to recall that we've heard of such bugs
before. Can you check for any updates from Sun that might affect
strtod()?
Nothing found yet. But searching the web for "solaris strtod" yields,
that solaris strtod might behave in a special way...
Regards,
Martin
---(end of broadcast)---
TIP 8: explain analyze is your friend
thread at build time. The dynamic
linker will resolve the dependency on libpthread.so (via libpq.so) at
runtime.
Regards,
Martin
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
nment
variables instead of the database encoding.
It would also be nice to call "set \encoding" to match the locale psql
was called under, at least when it is called interactively.
Thanks and have a nice day!
Martin
--
Martin Pitt http://www.piware.de
U
PostgreSQL's TEXT field
Do you consider adopting them in the official version?
Thanks a lot and have a nice day!
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developerhttp://www.ubuntulinux.org
Debian GNU/Linux Developer http://www.debian.org
Hi again!
Martin Pitt [2004-11-01 9:04 +0100]:
> Neil Conway [2004-11-01 14:06 +1100]:
> > 20pg_dump_datestyle seems redundant (we already set DateStyle to ISO in
> > pg_dump).
I will look at this and remove it if appropriate. Thanks for the hint.
> > ISTM the right fix
ly in arch head:
http://arch.debian.org/arch/pkg-postgresql/postgresql/
The three 25contrib* were split out of the 25contrib patch currently
in 7.4.6-2. The dbf2pg patches were added by me yesterday. I will
probably make a new upload soon, though.
Thanks for considering and have a nice day!
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developerhttp://www.ubuntulinux.org
Debian GNU/Linux Developer http://www.debian.org
signature.asc
Description: Digital signature
Cast int to domaim based on bit(n) works quite strange.
CREATE DOMAIN kat bit(40) NOT NULL;
SELECT 7::bit(40), 7::kat;
--on Win (7.5devel) and Linux (8.0.0b4)
bit | kat
0111 |
1000
--on Linux (7.4.6)
bit | kat
000
only used on PostgreSQL developer's
machines, so it might be a good idea to fix then eventually.
Thanks for considering and for your great work and have a nice day!
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developerhttp://www.ubuntulinux.o
The following bug has been logged online:
Bug reference: 1439
Logged by: Martin Drinck
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system: Win XP
Description:unable to create more than 21 database connections
Details:
Im trying to connect
Hi PostgreSQL developers!
We recently got the bug report below. Do you agree that documenting
~/.pgpass in psql(1) is a good idea?
Thanks for considering and have a nice day!
Martin
- Forwarded message from Jari Aalto <[EMAIL PROTECTED]> -
Subject: Bug#308535: postgresql-client:
, since SQL standard does
not allow to use double quotes for strings; the single quote is
reserved for that.
[...]
- End forwarded message -
The "joe" typo should be fixed in any case, and I also think that the
password example is a good idea. What do you think about this pat
Hi!
Tom Lane [2005-05-13 9:49 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > We recently got the bug report below. Do you agree that documenting
> > ~/.pgpass in psql(1) is a good idea?
>
> On that theory we'd have to replicate large parts of the libpq
>
.4 docs. Can this case be handled more gracefully in
7.4? Maybe the check from 8.0 can be ported to 7.4?
Thanks and have a nice day!
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntulinux.org
Debian Developerhttp://www.debian.org
psql_bug_cacheid.sh
Hi!
Tom Lane [2005-06-02 11:46 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > I found out that activating
>
> > log_parser_stats = true
> > log_planner_stats = true
> > log_executor_stats = true
> > log_statement_stats = true
>
> >
fix integer timestamps, or if
that is not possible, at least support selecting integer or float time
stamps at runtime (maybe as a postmaster option). Can this be done in
any way?
Thanks in advance for any thought and have a nice day!
Martin
[1] http://bugs.debian.org/311533
--
Martin Pitt
Hi!
Andrew - Supernews [2005-06-10 23:29 -]:
> On 2005-06-10, Martin Pitt <[EMAIL PROTECTED]> wrote:
> >> As per conversation in #postgresql in freenode, it has been found that
> >> this seems to manifest on pgsql compiled using integer-datetime;
> >> float
Hi Tom!
Tom Lane [2005-06-11 13:13 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > This would require that support for both int and float timestamps is
> > present in the postmaster, but wouldn't require an immediate dump and
> > reload of all databases. W
ol/mail/postgres
PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin
INPUTRC=/etc/inputrc PWD=/var/lib/pgsql LANG=cs_CZ.UTF-8 SHLVL=1
HOME=/var/lib/pgsql LOGNAME=postgres PGDATA=/var/lib/pgsql/data
Is it a bug in PostgreSQL or am I missing something?
--
Regards,
Martin Edlma
to initdb.
Aborted
As long as I know I have to put some key in configure command. I have
tried with |--enable-nls and ||--enable-recode, but that just did not work.|
Cann you please tell me, how cann I make this work.
Best regards,
Martin Nikolov.
P.S. Sorry for my terrib
Hi PostgreSQL developers!
While cleaning up the postgresql bug reports in Debian, I stumbled
over the following gem. Do you know about this problem, and is it
still an issue for 8.0 and 8.1?
Thanks in advance,
Martin
--- http://bugs.debian.org/275207
I have a postgresql server which runs
\
--with-gnu-ld \
--with-tclconfig=/usr/lib/tcl$(TCL_VER) \
--with-tkconfig=/usr/lib/tk$(TCL_VER) \
--with-includes=/usr/include/tcl$(TCL_VER):/usr/lib/R/include \
--with-pgport=5432 \
Thanks in advance!
Martin
Hi Tom!
Tom Lane [2005-09-29 17:50 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > On almost all Debian platforms the horology test for 8.0.3 fails.
>
> Before PG 8.0, I'd have said you were running with a timezone library
> that didn't understand about
nion.
Since this is by no way Debian specific, would you be interested to
fix this upstream as well?
Thanks for considering and have a nice day!
Martin
--- snip ---
--- postgresql-7.4.7-old/src/backend/libpq/auth.c 2003-12-20
18:25:02.0 +
+++ post
eld which translates to PostgreSQL's "text" data type.
They are not Debian specific in any way and probably useful for all
other users, too. Can you please consider applying them upstream?
Thanks in advance!
Martin
--
Martin Pitthttp://www.piware.de
Ubuntu Developer htt
Hi again,
Martin Pitt [2005-10-06 20:34 +0200]:
> A long time ago some Debian user sent me two patches to improve the
> dbf2pg conversion tool (in contrib). These are applied in the Debian
> packages for quite a while now without any problems. I forwarded them
> here some time ago
ke
for debugging.
Thanks and have a nice day!
Martin
--
Martin Pitthttp://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
In a world without walls and fences, who needs Windows and Gates?
signature.asc
Description: Digital signature
The following bug has been logged online:
Bug reference: 1963
Logged by: Martin Pitt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1beta3
Operating system: Debian
Description:SSL certificate permission check is too strict
Details:
Currently the postmaster
Hi Tom!
Tom Lane [2005-10-14 11:38 -0400]:
> "Martin Pitt" <[EMAIL PROTECTED]> writes:
> > Currently the postmaster requires the private SSL key file to have the same
> > owner as the postmaster, and no permissions for group and others. However,
> > t
Hi Tom!
Tom Lane [2005-10-16 0:41 -0400]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > At least the certificate could be permitted to be owned/in group root.
> > I cannot see how this should weaken the certificate's security.
>
> Postgres doesn't ru
The following bug has been logged online:
Bug reference: 2009
Logged by: Martin Pitt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: Linux
Description:Unqouted dashes in manpages
Details:
The PostgreSQL manpages currently do not quote
Hi Peter!
Peter Eisentraut [2005-10-30 0:19 +0200]:
> Am Samstag, 29. Oktober 2005 02:36 schrieb Martin Pitt:
> > The PostgreSQL manpages currently do not quote the dash (they contain '-'
> > instead of '\-', as mandated by manpages). Since this produces a diff
Hi PostgreSQL developers!
In Debian we recently received the bug report below, but since I
don't know the guts of PostgreSQL so well, could someone please take a
look at it?
Thanks in advance!
Martin
- Forwarded message from Michael Blake <[EMAIL PROTECTED]> -
Subject:
upstream?
Thanks!
Martin
- Forwarded message from Emanuele Rocca <[EMAIL PROTECTED]> -
Subject: Bug#338645: postgresql-contrib-8.1: dbf2pg silently ignores the -F and
-T options
Reply-To: Emanuele Rocca <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Date: Fri, 11 Nov 2005 20:04:3
The following bug has been logged online:
Bug reference: 2077
Logged by: Martin Pelikan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4
Operating system: Gentoo Linux 2.6.14-gentoo-r2
Description:Hiding databases which I am not owner
Details:
We have had
Hi again!
Martin Pitt [2005-09-29 23:08 +0200]:
> Hi!
>
> On almost all Debian platforms the horology test for 8.0.3 fails.
> Sometimes it works on a platform, sometimes not, I did not yet find a
> pattern, but most often it fails with something like
> [...]
I now think I
Hi Tom!
Tom Lane [2005-12-20 12:49 -0500]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > So it seems that the test suite uses the timezone files from the
> > installed system instead of the files in the temporary installation in
> > the regression test directory.
>
Hi!
Martin Pitt [2005-12-20 21:23 +0100]:
> Maybe I did something wrong with the configure options. That bug is
> reproducible with the pristine upstream 8.1.1 tarball and doing:
>
> ./configure --prefix=/usr --mandir="\${prefix}/share/man" \
> --sysconfdir=/etc
d of mangling the path somewhere in the middle,
the test suite should just prepend the tmp_check path.
It seems that the needs of the upstream tarball handling and the needs
of packaging differ somewhat. But instead of hacking in the interiors
of path handling, I will rather try another easy w
Hi!
Tom Lane [2005-12-20 17:16 -0500]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > ./configure --libdir=3D/usr/lib/postgresql/8.1/lib --bindir=3D/usr/lib/pos=
> > tgresql/8.1/bin
>
> > is enough to reproduce the problem. With only --libdir, it works, and
> &g
nstallation...)
>
> Debian's policy is to do --disable-rpath also, which I hope Martin is
> doing but honestly havn't gone back and checked on lately. :)
Right, rpath is evil, and Debian packages have always disabled it.
Merry christmas,
Martin
--
Martin Pitt
ian.org/343616
Thank you for considering this, and have a merry christmas!
Martin
--
Martin Pitthttp://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
In a world without walls and fences, who needs Windows and Gates?
diff -ruN postgresql-8.
Hi Tom!
Tom Lane [2005-12-23 17:38 -0500]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > I'm fine with dropping --bindir, --libdir, --datadir, but at least the
> > arch-independent and arch-dependent prefix should work. I do not want
> > to put all arch-in
Thank you in advance for any idea,
Martin
[1] http://bugs.debian.org/343622
--
Martin Pitthttp://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
In a world without walls and fences, who needs Windows and Gates?
signature.asc
Descriptio
the manual way.
I just reported it here since other distributions have the same
problem, so knowing the official upstream approach is always helpful.
:)
Thank you,
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntulinux.org
Debian Developerhttp:/
Hi!
Tom Lane [2005-12-29 22:20 -0500]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > I recently got a rather interesting Debian bug [1]: When upgrading a
> > pre-8.1 database to 8.1, the upgrade messes up permissions if the old
> > database had users and groups with
under Windows.
Any idea?
Thank you!
Martin
- Forwarded message from fgaroso <[EMAIL PROTECTED]> -
To: [EMAIL PROTECTED]
From: fgaroso <[EMAIL PROTECTED]>
Subject: Bug PostgreSQL
Date: Wed, 1 Feb 2006 14:12:04 -0200
X-Spam-Status: No, score=2.1 required=4.0 tests=BAYES_50,DNS_F
Hi PostgreSQL developers,
the bug report below was recently sent to Debian. The details and my
reply are at http://bugs.debian.org/358546, the executive summary is:
pg_ctl's -w option does not honour postgresql.conf's
unix_socket_directory configuration (and neither $PGHOST).
Thank
The bug trail in [1] contains a followup from Tom that ignoring
SIGPIPE is specifically intended. Is there any document which states
the reason for that?
Thanks in advance for any insight,
Martin
[1] http://bugs.debian.org/255208
[2] http://archives.postgresql.org/pgsql-hackers/1997-
Hi PostgreSQL developers,
the bug report below was recently sent to Debian. The details and my
reply are at http://bugs.debian.org/358546, the executive summary is:
pg_ctl's -w option does not honour postgresql.conf's
unix_socket_directory configuration (and neither $PGHOST).
Thank
23:51:51 +0200, "Guillaume Smet" <[EMAIL PROTECTED]> wrote:
>> From: Martin Marques
>> I encountered a rare BUG in the way PG is logging. Let me first enlight
> with some configuration I have and PG version:
>
> Perhaps I'm missing something
I encountered a rare BUG in the way PG is logging. Let me first enlight with
some configuration I have and PG version:
prueba2=> SELECT version();
version
---
The following bug has been logged online:
Bug reference: 5495
Logged by: Martin Edlman
Email address: edl...@fortech.cz
PostgreSQL version: 8.4.4
Operating system: Scientific Linux 5.5 (RHEL)
Description:RI/FK on self and inherited table
Details:
I have a table
fallback
lookup in /etc/postgresql/ or similar.
Would you accept a patch which adds a configure option for the path of
a system wide root certificate?
Thank you,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org
Hello PostgreSQL developers,
Martin Pitt [2010-08-17 6:49 +0200]:
> I received a request to support system-wide root certificates in
> libpq. Right now it only looks in ~/.postgresql/root.crt, but since
> such certificates are usually set up system wide and be maintained by
> the s
Magnus Hagander [2010-08-20 15:07 +0200]:
> Please add this to
> https://commitfest.postgresql.org/action/commitfest_view/open
Done, thanks!
https://commitfest.postgresql.org/action/patch_view?id=364
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Dev
The following bug has been logged online:
Bug reference: 5770
Logged by: Martin Edlman
Email address: edl...@fortech.cz
PostgreSQL version: 9.0.1
Operating system: Scientific Linux 5.5 (RHEL)
Description:Foreign key violation after insert
Details:
Hello,
I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tom,
> "Martin Edlman" writes:
>> I encountered this problem during migration of the database from PgSQL 8.4
>> (where it works) to PgSQL 9.0.1.
>
> For me, this example fails on both 8.4 and 9.0. It works o
m bug at all. Can you please open a Debian or
Ubuntu bug report, with the output of
ls -ld /sbin /bin /usr/sbin /usr/bin
? The error message suggests that one or more of these directories are
world-writable.
Thank you,
Martin
--
Martin Pitt| http://www.piware.de
Ubun
The following bug has been logged online:
Bug reference: 5784
Logged by: Martin Atukunda
Email address: matl...@gmail.com
PostgreSQL version: 8.4
Operating system: Linux
Description:CREATE INDEX USING GIN complains about array containing
null values yet none exist
t of this would be to:
1. copy out all the rows
2. truncate the Tables
3. then create the index
4. copy in the rows
- Martin -
On Sun, Dec 5, 2010 at 7:58 PM, Andres Freund wrote:
> On Sunday 05 December 2010 13:29:35 Andres Freund wrote:
> > On Sunday 05 December 2010 13:07:23 Martin Atukunda wrote:
> > > > Due to the wonders of MVCC the old row is still available in the
> heap.
> > >
101 - 200 of 254 matches
Mail list logo
