idea.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Description:
Postgresql 9.3 from OpenSCG dose not start automaticly when enalbled in
system runlevel. It must by started manualy.
Hello!
Bugs in the OpenSCG packaging should be reported to OpenSCG, to make
sure they actually spot them and can fix it before the release.
--
Magnus Hagander
Me: http
On Sun, Aug 25, 2013 at 9:05 AM, TAKATSUKA Haruka haru...@sraoss.co.jp wrote:
Thanks for the response.
On Sat, 24 Aug 2013 17:04:21 +0200
Magnus Hagander mag...@hagander.net wrote:
(1) create new standby server dir by pg_basebackup without -x
(2) start new standby server
(3
-
since AFAICT this error gets thrown only after all the data has been
sent arlready.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
longer than expected. We expect it
to be up again fairly soon.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Hi!
There was a bug in the website code caused by an upgrade. This was fixed
yesterday, so please try again now.
/Magnus
On Jun 20, 2013 5:09 PM, luk...@novosoft.net wrote:
The following bug has been logged on the website:
Bug reference: 8241
Logged by: Oksana
Email address:
On Feb 5, 2013 6:20 PM, yogesh.khandel...@emc.com wrote:
The following bug has been logged on the website:
Bug reference: 7852
Logged by: Yogesh Khandelwal
Email address: yogesh.khandel...@emc.com
PostgreSQL version: 9.0.8
Operating system: Linux
Description:
hi,
On Sun, Jan 20, 2013 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
+ PGresult *res = ExecuteSqlQueryForSingleRow(fout, SELECT
pg_is_in_recovery());
That function call needs to be schema-qualified for security.
Applied and backpatched
On Tue, Jan 15, 2013 at 10:35 PM, Magnus Hagander mag...@hagander.net wrote:
On Tue, Jan 15, 2013 at 12:13 AM, j...@tanga.com wrote:
The following bug has been logged on the website:
Bug reference: 7809
Logged by: Joe Van Dyk
Email address: j...@tanga.com
PostgreSQL
of saying could not open file, could we find a way to
say this is an unlogged table on a slave, it's not going to work?
We can fix pg_dump the easy way, but what about custom tools...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs
that needs to be clarified in the documentation if people
find it confusing.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On Mon, Jan 7, 2013 at 4:41 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Mon, Jan 7, 2013 at 1:32 AM, Tom Lane t...@sss.pgh.pa.us wrote:
emes...@redhat.com writes:
* restore.sql includes DROP statements for each object even tough -c flag
was not given
access to any
permissions received by being in the Administrators or Power Users
group for example.
You can verify it by for example attempting to COPY to a file that
only administrators have access to (access must be granted through the
group, of course)
--
Magnus Hagander
Me: http
, by
e.g doing a VACUUM FULL on the table about to be copied.
A straightforward fix is to allow sendFile() to ignore ENOENT. Patch
attached.
Looks good to me. Nice spot - don't tell me you actually ran into it
during testing? :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
people, not us.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, you need to use at least the
same version as the one you created the dump with.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
fallout from a patch that went into
the website codebase a few days ago.
I'll look at getting it fixed in a few hours. Sorry about that!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
what the reason for not starting
is - which in this case is that PostgreSQL has no idea what
listen_addresse is, since it's spelled wrong.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
?)
Oh, and what do you actually mean by long time?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
of, but it's always a possible side-effect from
something else - so it's always worth applying the latest patches.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
as listed, at
least for me...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
pushing merge commits, if
that has been enabled. But there are no such rules enabled for the
pldebugger one.
Note of course, which you probably already know, that doing a force
push may cause problems for others who have cloned the repository...
--
Magnus Hagander
Me: http://www.hagander.net
try to keep the environment for the query tool connection as
clean as possible. So if it's reasonably easy to do this (I haven't
looked at the code, but I would assume it is), then I suggest doing
that *and* backpatching it so it'll go into the next version of the
stable branch.
--
Magnus
my
problem of installation. Thank you.
I have no idea what HM2 is, but if you are a customer of theirs, it
sounds like you should bring it up with them?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Jun 27, 2012 8:26 AM, Craig Ringer ring...@ringerc.id.au wrote:
On 06/26/2012 06:26 PM, Dave Page wrote:
Any ideas for a one-liner to add? I'm struggling to find nice wording,
that doesn't invite people to report issues without investigating
themselves first:
* If you need help, please
On Jun 27, 2012 8:42 AM, Craig Ringer ring...@ringerc.id.au wrote:
On 06/27/2012 02:33 PM, Magnus Hagander wrote:
... where that provides the common-issues list, a pointer to look at
the installation log, then a report template for cases where it wasn't one
of the common quick-fixes.
I'm
couldn't deal with, because they simply can't know the
future...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Fri, Jun 15, 2012 at 7:33 PM, Mark Schneider
m...@it-infrastrukturen.org wrote:
Am 15.06.2012 07:56, schrieb Magnus Hagander:
On Wed, Jun 13, 2012 at 2:45 AM,m...@it-infrastrukturen.org wrote:
The following bug has been logged on the website:
Bug reference: 6689
Logged
on different ports still.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, and what are you expecting to happen?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Mon, Jun 11, 2012 at 6:01 PM, David Fetter da...@fetter.org wrote:
On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
On Mon, Jun 11, 2012 at 5:14 PM, da...@fetter.org wrote:
The following bug has been logged on the website:
Bug reference: 6687
Logged
On Mon, Jun 11, 2012 at 6:14 PM, David Fetter da...@fetter.org wrote:
On Mon, Jun 11, 2012 at 06:04:22PM +0200, Magnus Hagander wrote:
On Mon, Jun 11, 2012 at 6:01 PM, David Fetter da...@fetter.org wrote:
On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
On Mon, Jun 11, 2012
/pg_upgrade.zip - please see if that
one works for you.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
\pg_upgrade_utility.log SUCCESS Offset: 396 Length: 16
183 3:48:01 p.m. cmd.exe:99396 OPEN
C:\ccviews\pg_upgrade_utility.log SHARING
VIOLATION Options: Open Access: 0012019F
We probably need to send these to different logfiles. Bruce?
--
Magnus Hagander
Me: http
it.
I think process title seems reasonable. We do that for archiver for
example, to tell you where it's writing, don't we?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
This is clearly not a bug...
I have no idea what Version Tracker is, or where you got that link
from, but postgresql 9.0.1 is an out of date version. You can find
downloads for all current versions at
http://www.postgresql.org/download/.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
for.
//Magnus
On Sun, Mar 4, 2012 at 14:02, Ronald Hofmann pro...@jumbosoft.de wrote:
So you say 9.01 for 10.4 (from 2007) is current?
No thank you, I chose MySql
Regards
---
Am 04.03.2012 um 12:44 schrieb Magnus Hagander mag...@hagander.net:
On Fri, Mar 2, 2012 at 06:41, pro...@jumbosoft.de
better. Fix applied.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
website is down (tried to visit the pgpool page), and I didn't
know where else to report it.
This is not a PostgreSQL bug. Please see threads on the pgsql-www
mailinglist (archives.postgresql.org/pgsql-www).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com
page PgFounfry id out. I want to download the npgsql, but I cannot.
This is not a PostgreSQL bug.
(It is known that pgfoundry is down - see the pgsql-www mailinglist
where such issues are discussed)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent
postgres_cifs_kaz_1[15812]: [2-2] [local] 15812
2011-12-30 03:00:26.511 PST STATEMENT: CREATE DATABASE KazDB
Please help to make it work.
PostgreSQL does not support data directory over CIFS.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via
On Mon, Jan 2, 2012 at 21:14, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Mon, Jan 2, 2012 at 17:27, anjali_...@yahoo.co.in wrote:
PST ERROR: could not fsync file base/16409: Invalid argument Dec 30
03:00:26 devok64-8 postgres_cifs_kaz_1[15812]: [2-2
On Mon, Jan 2, 2012 at 21:28, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Mon, Jan 2, 2012 at 21:14, Tom Lane t...@sss.pgh.pa.us wrote:
I'm wondering what's your basis for asserting we don't support CIFS in
general? It's probably not terribly bulletproof
(maybe postgres) and tries to use it in another. That's a really
easy mistake to make...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
On Mon, Nov 21, 2011 at 19:03, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
Il giorno lun, 21/11/2011 alle 18.59 +0100, Magnus Hagander ha scritto:
So a simple extension of the check to be for both ENOENT and ENOTDIR
would work, right?
In this case, yes...
Ok, I've applied this quick-fix
website code that applied HTML escapes to plaintext emails, which in
the end caused double escaping. I've just pushed a fix for this, so from
now on bugreports won't do that.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Nov 21, 2011 8:29 AM, Diego Elio Pettenò flamee...@flameeyes.eu
wrote:
The following bug has been logged online:
Bug reference: 6302
Logged by: Diego Elio Pettenò
Email address: flamee...@flameeyes.eu
PostgreSQL version: 9.1.1
Operating system: Gentoo Linux
On Mon, Nov 21, 2011 at 18:43, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
Il giorno lun, 21/11/2011 alle 09.08 +0100, Magnus Hagander ha scritto:
What actual error do you get?
ENOTDIR, sorry but I don't really want to break my system again just to
show the strerror output ;)
So
.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
definitely accept a docs patch to
clarify what happens, because I agree it's confusing.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
for, that
is not the same as HAVE_LONG_LONG_INT_64?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
or flags, you get two
completely separate heaps in the app. Which is exactly the reason why
we added that function to libpq.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
the (NP) flag to not propagate
inheritance or something?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
picked were more or less still guestimates. So I
think it's just a mistake in that, and should be changed.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
src/interfaces/libpq/fe-connect.c.
This appears to be a documentation mistake that goes back to at least
version 8.4.
Yup, it's a doc bug alright. It goes back to 8.4, where that table was added.
I've applied a fix for this, will be in the next release. Thanks for reporting!
--
Magnus
On Wed, Jun 29, 2011 at 23:52, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Wed, Jun 29, 2011 at 15:31, Steve Haslam araq...@googlemail.com wrote:
= select pg_stat_reset_shared(null)
*server segfault*
Thanks for the report - fixed, and will be in next
nice way though...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
many people that
we need to be even more clear than that. Like specifically saying that
changing it back to off will make legacy applicatoins work again.
Given that *so* many apps use it... And people don't look at warnings
;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
and recompiling, of course). If we didn't send those to the
eventlog, they would be completely lost since there is no stderr
available to a windows service.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs
SMB mounts anyway. It
requires a local NFTS filesystem. SMB mounts cannot be trusted for
databases.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
perhaps? Or maybe
something blocking your access?
Given the timestamp of the email, I would guess this was sent during
the big hub.org outage yesterday, at which point all things pgfoundry
were offline. So I think it's safe to saythat things have been fixed
now.
--
Magnus Hagander
Me: http
to_char(current_date, 'TMMonth ');
to_char
---
MäRz 2011
I also can reproduce this at a FreeBSD 7.0-STABLE.
IIRC, the FreeBSD locales at least used to be pretty much broken for
UTF8. Can you try and see if you get the same problem in a non-UTF8
locale?
--
Magnus Hagander
Me
to the error message...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, it will. On the port that you specified.
It will not accept connections on a port it's not configured.
Regardless of client, whether it's a replication client, or psql, or
pgadmin, or your application.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs
On Thu, Dec 16, 2010 at 02:25, Josh Berkus j...@agliodbs.com wrote:
On 12/15/10 4:58 AM, Magnus Hagander wrote:
In any case, a doc patch would be the right thing for the back branches.
I can look at this too (yes, I know we just wrapped, but I'm working
down the backlog :S). You mean
On Fri, Oct 29, 2010 at 19:56, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Fri, Oct 29, 2010 at 10:01, Josh Berkus j...@agliodbs.com wrote:
Mind you, we *also* need a doc patch. (This parameter is only available if
PostgreSQL was built with SSL support
them,
http://archives.postgresql.org/pgsql-committers/2007-03/msg00144.php
Magnus, was this intentional by any chance?
Nope, not that I can recall. Looks like an oversight.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing
crashing..
Any chance it's a third party module that you didn't recompile for 9.0?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
of the process, just like the title does on Unix. Or you
can look up the process id in the pg_stat_activity view to identify
it.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
that depend on a
specific compile flag. That would make life easier on automated tools
*and* on people sitting down at a new installation.
Thoughts?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
4.3.3-5ubuntu4) 4.3.3, 64-bit
(1 row)
postgres=# show ssl_ciphers;
ERROR: unrecognized configuration parameter ssl_ciphers
So, did ssl_ciphers go away on purpose? If so, why? If not, why isn't it
accessible?
Are you sure you're on an SSL enabled build?
--
Magnus Hagander
Me: http
On Tue, Oct 5, 2010 at 15:18, Magnus Hagander mag...@hagander.net wrote:
On Tue, Oct 5, 2010 at 11:01, Magnus Hagander mag...@hagander.net wrote:
On Sun, Oct 3, 2010 at 18:30, Alan T DeKok al...@freeradius.org wrote:
Tom Lane wrote:
Hm ... seems to me that is a network security problem
On Tue, Oct 5, 2010 at 19:11, Alan T DeKok al...@freeradius.org wrote:
Magnus Hagander wrote:
Actually, nevermind that one. Here's a patch I worked up from your
description, and that turns out to be fairly similar to yours in what
it does I think - except I'm not rearranging the code
as attachment or publish it as a git
repository I can fetch from?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Tue, Oct 5, 2010 at 11:01, Magnus Hagander mag...@hagander.net wrote:
On Sun, Oct 3, 2010 at 18:30, Alan T DeKok al...@freeradius.org wrote:
Tom Lane wrote:
Hm ... seems to me that is a network security problem, not our problem.
Who's to say one of the spoofed packets won't pass
On Tue, Sep 28, 2010 at 03:28, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
Magnus Hagander mag...@hagander.net writes:
But how likely is that to bite us elsewhere then?
Initdb works well if the link is a junction (mklink /J).
We use junctions for tablespaces, but don't use symbolic
On Tue, Sep 28, 2010 at 11:08, Magnus Hagander mag...@hagander.net wrote:
On Tue, Sep 28, 2010 at 03:28, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
On Mon, Sep 27, 2010 at 11:14 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I think this is a Microsoft bug and it's their problem to fix
because built with MSVC 2008 :-( .
Ouch.
We could work around it in this place (we could specifically ignore
the file exists error on the mkdir call), I guess. But how likely is
that to bite us elsewhere then?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com
On Fri, Sep 24, 2010 at 00:41, Peter Eisentraut pete...@gmx.net wrote:
On tor, 2010-09-23 at 08:36 +0200, Magnus Hagander wrote:
I wonder if we want to have a default value for this rather than
disabling it when it's not specified by configure. But is there any
kind of reasonable default
of reasonable default that's not going to be
platform/distribution specific?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
. Are you saying it's fully reproducible?
I don't recall if we did any specific changes around this for 9.0, did we?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
On Tue, Aug 24, 2010 at 11:01 AM, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
On Tue, Aug 24, 2010 at 5:25 PM, Magnus Hagander mag...@hagander.net
wrote:
There might be issues to detach/reattach shared memory on Windows.
We've seen this on and off before. Are you saying it's fully
installation than anything.
Maybe you have messed up the PATH variable.
Seems this is XP embedded? Does it even come with cacls?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
-cert-dir=/etc/postgresql-common, and confirm that in
the latter case root.crt gets picked up from
/etc/postgresql-common/ if it's not in ~/.postgresql/.
Hi!
Please add this to https://commitfest.postgresql.org/action/commitfest_view/open
--
Magnus Hagander
Me: http://www.hagander.net/
Work
with support for the CRL as well, since it goes together with the root
cert ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
yet to see if I agree with the fix as well. Hope to get there soon.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
of a bug
report in a table somewhere just to look for duplicates. We can
expire it after just a minute or so. That'll catch the *exact*
duplicates. It could catch partial ones, too.
I'll stick that on the TODO list for the new website ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
On Fri, Jul 9, 2010 at 04:58, Craig Ringer cr...@postnewspapers.com.au wrote:
On 8/07/2010 6:31 PM, Magnus Hagander wrote:
On Thu, Jul 8, 2010 at 03:10, Craig Ringercr...@postnewspapers.com.au
wrote:
IIRC on Windows client certificates live in
%APPDATA%\.postgresql\
That's a typo
lot of thinsg we can rule
out as the culprits then :-)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
environment variable or connection string parameter. See
http://www.postgresql.org/docs/9.0/static/libpq-connect.html, for the
parameters sslcert and sslkey. Or
http://www.postgresql.org/docs/9.0/static/libpq-envars.html for the
respective environment vars.
--
Magnus Hagander
Me: http
says it'll
always return ENOENT on failure. Seems to me Windows is confused, but
I'm not entirely sure how.
Can you try specifying an explicit file say directly in c:\, just to
see if that works?
BTW, if you post bug reports to -bugs, it'll make a lot more people see them.
--
Magnus Hagander
Me
!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
than manually hacking the dump...
yeah. There are (supposedly?) a lot of *other* cases where using an
old version of pg_dump won't work. At least we reserve the right for
it to be.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs
can get that done for 9.0 (even if we call it
a bugfix) due to lack of time over the next couple of weeks.
(and yes, I intend to get back in on the rest of this thread as well
once I've cleared my pgcon-induced backlog)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill
On Tue, May 25, 2010 at 18:44, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Tue, May 25, 2010 at 17:48, Tom Lane t...@sss.pgh.pa.us wrote:
Craig Ringer cr...@postnewspapers.com.au writes:
Bug 5245 is not the same issue.
BTW, does anyone know exactly how
something we will need to push back for a full release, which would
mean 9.1. What would be good is if we can collect a list of interop
issues and collect test-cases for them, because given the state of the
openssl documentation it really comes down to having fairly detailed
test-cases...
--
Magnus
” time zone.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
afterwards. What would you suggest in this case?
kill -9 on a client will make the postmaster restart the whole
process, so yes, it's a very heavy operation.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs
break Almaty. There's no real easy way for us to find the difference
between those, since we're just matching on those two strings.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
1 - 100 of 496 matches
Mail list logo
