Hi Heikki,
On Mon, 27 Jun 2011 at 12:10, Heikki Linnakangas wrote:
Max, you're the maintainer of the PostgreSQL SuSE RPMs, right?
my first name is Reinhard, but aside from that, you are right. ;)
Can you comment on the above?
I enabled it many years ago when (IIRC) it was needed in conjun
On Tue, 28 Jun 2011 at 10:40, Heikki Linnakangas wrote:
It seems to me you could just stop setting silent_mode. If you want
to capture any early errors at startup into a log file, like
silent_mode does to postmaster.log, you can redirect stdout and
stderr in the startup script. pg_ctl start -l
Hi Marc,
On Fri, 8 Nov 2002 at 09:59, Marc G. Fournier wrote:
> At this point, we are looking for confirmation that all the
> platforms are building and running the regression tests correctly,
v7.3b5 builds and passes the testsuite under SuSE Linux on the
following platforms:
i386, ia64
On Fri, 25 Aug 2006 at 10:20, Tom Lane wrote:
> If this were a bulletproof solution then I'd consider it anyway, but
> AFAICS it's got the very same vulnerabilities as the flag-file
> method, ie, if you RPM install or upgrade while your mountable data
> directory is offline, you can still get s
On Sat, 9 Sep 2006 at 15:57, Lamar Owen wrote:
> [...] or annoying the small number of people who NFS mount their
> datadirs?
This problem is not limited to NFS. It can happen with any FS just by
reversing (for whatever reason) the order of mounting the FS and
starting the PostgreSQL server.
Hi,
it appears all of PostgreSQL's binaries are linked against libreadline and
libncurses, but the only one that really needs them seems to be psql.
Is there a reason behind this other than that it might be easier to have
only one set of linker switches that can be used for everything?
cu
On Wed, 5 Nov 2003 at 13:28, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>
> > The SuSE PPC guru said that the PPC spinlock code we currently use
> > may behave erroneously on multiprocessor systems.
>
> What's his evidence for that claim?
Let's ask himself.
> The code we have
On Wed, 12 Jan 2005 at 16:29, Peter Eisentraut wrote:
> In the meantime I have received confirmation from Reinhard Max that
> his test methods match our requirements, so the list will be
> completed with the other platforms he reported in due time.
Today I've updated the RPMs on
On Wed, 12 Jan 2005 at 17:29, Reinhard Max wrote:
> The only failure I have to report is sles8-x86_64, where I am
> getting segfaults from psql during the regression tests.
The segfault in a call to snprintf somewhere in libpq's kerberos5
code. So when I leave out --with-krb5 it c
On Wed, 12 Jan 2005 at 18:20, Reinhard Max wrote:
> I am still not sure whether the kerberos library, glibc, or
> PostgreSQL is to blame, or if it's a combination of bugs in these
> components that triggers the segfault.
The problem is, that the heimdal implementation of ker
Sorry for following up to myself once more...
On Wed, 12 Jan 2005 at 19:36, Reinhard Max wrote:
> The problem is, that the heimdal implementation of kerberos5 used on
> sles8 needs an extra include statement for com_err.h in
> src/interfaces/libpq/fe-auth.c to get the prot
On Wed, 12 Jan 2005 at 20:28, Kurt Roeckx wrote:
> This is because the proper prototype is:
> extern char const *error_message (long);
>
> And C automaticly generates a prototype with in int instead.
>
> On 32 bit platforms this ussualy isn't a problem since both int and
> long are ussualy both
On Wed, 12 Jan 2005 at 14:59, Tom Lane wrote:
> That looks like a reasonable fix, but isn't it needed in
> backend/libpq/auth.c as well?
Yes, indeed:
auth.c: In function `pg_krb5_init':
auth.c:202: warning: implicit declaration of function `com_err'
cu
Reinhard
---
Simon,
On Wed, 12 Jan 2005 at 08:23, Simon Riggs wrote:
> Not sure what is going on here: why is SUSE not listed on the supported
> platforms list? (still)
>
> ...is it because Reinhard seems resistant
why do you think so?
> (after private conversation) to the idea of submitting a formal port
Tom,
On Wed, 12 Jan 2005 at 03:53, Tom Lane wrote:
> > ...or is it because his postings to ANNOUNCE that the port to SUSE
> > have gone unnoticed by those that compile the supported platforms
> > list?
>
> If he insists on posting such routine stuff to pgsql-announce, he
> should not be too s
On Tue, 18 Jan 2005 at 11:53, Marc G. Fournier wrote:
> ... if someone knows how to safely remove a branch that has had no
> commits made to it, please let me know,
a little bit of googling brought me to this:
http://lists.gnu.org/archive/html/info-cvs/2003-11/msg00166.html
--- snip ---
> How
16 matches
Mail list logo
