_salt('md5') ?]
This, however, might be a good idea. People should of course always
read the documentation, but having the examples including the "best
practice" would probably be a good 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
cription:
>
> 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.
On Sun, Aug 25, 2013 at 9:05 AM, TAKATSUKA Haruka wrote:
> Thanks for the response.
>
> On Sat, 24 Aug 2013 17:04:21 +0200
> Magnus Hagander wrote:
>
>> > (1) create new standby server dir by pg_basebackup without -x
>> > (2) start new standby server
>&g
e first case, throwing a hard error
seems quite reasonable, but if it's repeatable, perhaps there is
something better we can do?
Also, while we definitely need a sanity check at this point, might it
be worth it to put a second check earlier in the process as well -
since AFAICT this error
lem with a simliar thing for
postgresql.conf).
Perhaps the OP has a specific usecase to share where this would
actually be both safe and useful?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To m
n 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-bugs
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, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8241
> Logged by: Oksana
> Email address: luk...@nov
On Feb 5, 2013 6:20 PM, 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,
>
> I've deployed
On Sun, Jan 20, 2013 at 4:59 PM, Tom Lane wrote:
> Magnus Hagander writes:
>> + PGresult *res = ExecuteSqlQueryForSingleRow(fout, "SELECT
>> pg_is_in_recovery()");
>
> That function call needs to be schema-qualified for security.
Applied and b
On Sun, Jan 20, 2013 at 4:59 PM, Tom Lane wrote:
> Magnus Hagander writes:
>> + PGresult *res = ExecuteSqlQueryForSingleRow(fout, "SELECT
>> pg_is_in_recovery()");
>
> That function call needs to be schema-qualified for security.
Ha! I wonder if I
On Tue, Jan 15, 2013 at 10:35 PM, Magnus Hagander wrote:
> On Tue, Jan 15, 2013 at 12:13 AM, wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 7809
>> Logged by: Joe Van Dyk
>> Email address: j...@tanga
be easy
enough to figure out at an early stage, too.
That said, it wouldn't hurt if we could make that error a little less
scary. Instead 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 c
On Mon, Jan 7, 2013 at 4:41 PM, Tom Lane wrote:
> Magnus Hagander writes:
>> On Mon, Jan 7, 2013 at 1:32 AM, Tom Lane wrote:
>>> emes...@redhat.com writes:
>>>> * restore.sql includes DROP statements for each object even tough -c flag
>>>> was not give
be possible.
I definitely think it's doing the right thing, but perhaps it's
something 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 li
tricted token and execute it as
that - so it will run as Administrator but without 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 (ac
an error. It's a
> fairly tight window, so it's difficult to run into by accident, but by
> putting a breakpoint with a debugger there it's quite easy to reproduce, by
> e.g doing a VACUUM FULL on the table about to be copied.
>
> A straightforward fix is to al
pg_restore version 8.4, 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:
- you should contact the django project
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
On Wed, Nov 7, 2012 at 3:53 PM, Magnus Hagander wrote:
> On Wed, Nov 7, 2012 at 3:30 AM, Denis Feklushkin
> wrote:
>> Hi!
>>
>> Bug reporting form:
>>
>> http://www.postgresql.org/support/submitbug/
>>
>> is not works - it slows down and fails with
finitely looks like 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-
elled listen_addresses wrong. If you look in your
logfile, it should clearly tell you 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/
W
ou configured the tcp keepalive on the slave
somehow?)
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
> The above error occured only one times.
> Is this problem fixed by latest package(8.3.20)?
Not that I know 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:
ng a force push, I believe.
There are rules in place to stop it from 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 re
t to 'homa', the result is Thomaas, which is clearly
wrong... The function as it's listed yields the result 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
is (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 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
ve 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 lis
On Jun 27, 2012 8:42 AM, "Craig Ringer" 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 on
On Jun 27, 2012 8:26 AM, "Craig Ringer" 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 review
with. But there would still be changes that
even those 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
wrote:
> Am 15.06.2012 07:56, schrieb Magnus Hagander:
>
>> On Wed, Jun 13, 2012 at 2:45 AM, wrote:
>>>
>>> The following bug has been logged on the website:
>>>
>>> Bug reference: 6689
>&g
g like
kernel level ip forwarding to rewrite the access, and actually run
PostgreSQL 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
On Mon, Jun 11, 2012 at 6:14 PM, David Fetter 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 wrote:
>> > On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
>> >> On Mon, Ju
On Mon, Jun 11, 2012 at 6:01 PM, David Fetter wrote:
> On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
>> On Mon, Jun 11, 2012 at 5:14 PM, wrote:
>> > The following bug has been logged on the website:
>> >
>> > Bug reference: 6687
&
em completely.. What is
happening, 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
t it
from http://www.hagander.net/tmp/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
that's coming from a shell redirect
somewhere?
> 142 3:47:47 p.m. pg_ctl.exe:98832 WRITE
> C:\ccviews\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
>
s an invented problem. We've never
> heard a complaint from the field about 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.
k
for.
//Magnus
On Sun, Mar 4, 2012 at 14:02, Ronald Hofmann 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 :
>
>> On Fri, Mar 2, 2012 at 06:41, wrote:
>&
esql-9.0.1.tar.bz2
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.
ing that feeding random data to the decrypt
functions should be expected to return random data out of previously
free()d areas? Surely you're not?
Obviouly, if you send in invalid data or an invalid key, it will
decrypt into incorrect data, that goes without saying. But it should
still be
ance."
Yeah, that seems 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
> Your projects 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: ht
iption:
>
> The web 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.red
On Mon, Jan 2, 2012 at 21:28, Tom Lane wrote:
> Magnus Hagander writes:
>> On Mon, Jan 2, 2012 at 21:14, Tom Lane wrote:
>>> I'm wondering what's your basis for asserting we don't support CIFS in
>>> general? It's probably not terribly bulletproof
On Mon, Jan 2, 2012 at 21:14, Tom Lane wrote:
> Magnus Hagander writes:
>> On Mon, Jan 2, 2012 at 17:27, 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] [local]
/16409": Invalid argument Dec 30
> 03:00:26 devok64-8 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: h
listed in this output?
>
> \dx+ pgcrypto
My guess is that the OP has installed the extension in one database
(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://ww
On Mon, Nov 21, 2011 at 19:03, Diego Elio Pettenò
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 th
> interpretation of what you did rather than showing us exactly what you
>
A fair amount of that garbling is unfortunately the fault of a bug in the
new 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 Mon, Nov 21, 2011 at 18:43, Diego Elio Pettenò
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 ;)
S
On Nov 21, 2011 8:29 AM, "Diego Elio Pettenò"
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
> Description:
ackend.
But I second and thid Heikkis recommendation that you need to get off
version 8.1 and onto something more recent as quickly as possible.
--
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
now - even if it may
be technically correct.
If we don't change it, we should 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/mailpref/pgsql-bugs
ied as commit 29259531, which apparently changed it from our own
implementation to the autoconf standard. And changed a whole bunch of places
from HAVE_LONG_LONG to HAVE_LONG_LONG_INT. Perhaps it just missed to update
the win32 file?
Just to be completely cetain, what behaviour is it we're looking 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/
VCRT will have it's own heap. But if the same
version is loaded through different paths, it will just use the same
copy. But when they're different versions or flags, you get two
completely separate heaps in the app. Which is exactly the reason why
we added that function to libpq.
--
n ntfs is, um, let's call it
interesting. Maybe it needs to specify 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
up table was your work to
> begin with --- do you remember anything about the reasoning for the
> Central America entries?
Hmm. not entirely. I know the initial round was basically all just
guesses. Then at some point we added tools/win32tzlist.pl. But IIRC
the actual timezones picked were
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 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 Wed, Jun 29, 2011 at 23:52, Tom Lane wrote:
> Magnus Hagander writes:
>> On Wed, Jun 29, 2011 at 15:31, Steve Haslam wrote:
>>> => select pg_stat_reset_shared(null)
>>> *server segfault*
>
>> Thanks for the report - fixed, and will be in next releases.
eset all the shared statistics.
Not in a very 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
gt;> Actually, I had something more like this in mind ...
>
> Great.
I wonder if this is something that's going to hit so 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 a
happen before we have opened the regular logfile will
be written to the eventlog if the server is running as a Windows
service. There is no way to turn that off (other than removing the
code and recompiling, of course). If we didn't send those to the
eventlog, they would be completely los
the service starts, it is in a
different session, and can thus not see your mount point.
That said, PostgreSQL is not supported over 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.red
ownload connector for .net . Thanks a lot.
>
> It works fine for me. Intermittent network issue 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 pgf
> # SET lc_time = "de_DE.UTF-8";
> SET
> # SELECT 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: 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
, but the user can't figure out that's why it
couldn't find the file? If so, the "could not get home directory" adds
some more information... We can't exactly expect the end user to know
that this is the only codepath that can lead 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
ing to accept replication from slaves.
Yes, 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.h
ight be worth looking at what the ODBC folks did though - they run
the actual protocol for the queries, but they use libipq for
connection setup and authentication (if found - they'll fallback on
doing simple auth etc if libpq isn't there)
--
Magnus Hagander
Me: http://www.ha
On Thu, Dec 16, 2010 at 02:25, Josh Berkus 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
On Fri, Oct 29, 2010 at 19:56, Tom Lane wrote:
> Magnus Hagander writes:
>> On Fri, Oct 29, 2010 at 10:01, Josh Berkus wrote:
>>> Mind you, we *also* need a doc patch. ("This parameter is only available if
>>> PostgreSQL was built with SSL support").
>
that not resetting the n_tuples_xxx fields was simply an
> oversight in Magnus' patch that added 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.
--
Mag
ot a part of
standard PostgreSQL 9.0, and this is the part that's 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/
ess, and find a handle
called something starting with "pgident" - that one will contain a
description 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:
how the value NULL?) on non-SSL
enabled builds. Same goes for all other parameters 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://w
x-gnu, compiled by GCC gcc (Ubuntu
> 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
> accessib
On Tue, Oct 5, 2010 at 15:18, Magnus Hagander wrote:
> On Tue, Oct 5, 2010 at 11:01, Magnus Hagander wrote:
>> On Sun, Oct 3, 2010 at 18:30, Alan T DeKok wrote:
>>> Tom Lane wrote:
>>>> Hm ... seems to me that is a network security problem, not our problem.
>&g
On Tue, Oct 5, 2010 at 19:11, Alan T DeKok 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 rearr
On Tue, Oct 5, 2010 at 11:01, Magnus Hagander wrote:
> On Sun, Oct 3, 2010 at 18:30, Alan T DeKok 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
es kind of hard to read posted inline that
way - any chance you can repost 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
IP source, correct? If we then looped
until we got one that validated as a proper packet, we'd still be able
to authenticate with that one, just throwing the invalid ones away.
Notice how the "read packet" part is moved inside the loop in his
suggestion.
--
Magnus Hag
On Tue, Sep 28, 2010 at 11:08, Magnus Hagander wrote:
> On Tue, Sep 28, 2010 at 03:28, Itagaki Takahiro
> wrote:
>> On Mon, Sep 27, 2010 at 11:14 PM, Tom Lane wrote:
>>> I think this is a Microsoft bug and it's their problem to fix, not ours.
>>
>> OK, but
On Tue, Sep 28, 2010 at 03:28, Itagaki Takahiro
wrote:
>> Magnus Hagander 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 links
t work 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.
On Fri, Sep 24, 2010 at 00:41, Peter Eisentraut 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 rea
when it's not specified by configure. But is there any
kind 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 connect to a 9.0 database.
> I don't see an error from \l, although it's entirely possible that
> some other backslash commands might fall over as a result of expecting
> datconfig to be there. I don't have pgAdmin handy to try, but if you
> are using a pre-9.0 version then yo
external command, operable program or batch
> file.
>
> This seems more a problem with your Windows 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/
On Tue, Aug 24, 2010 at 11:01 AM, Itagaki Takahiro
wrote:
> On Tue, Aug 24, 2010 at 5:25 PM, Magnus Hagander
> 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 reproduci
We've seen this on and off before. 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-
ot specified), as well as with
> --with-ssl-root-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/
ould have to come
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
;if (conn->pghostaddr)".
>
> That's really a definitional change, but it seems like a reasonable one
> to me. Magnus, what do you think?
Yeah, I think it is, but I haven't had the time to look into the code
yet to see if I agree with the fix as well. Hope to
On Fri, Jul 9, 2010 at 04:58, Craig Ringer wrote:
> On 8/07/2010 6:31 PM, Magnus Hagander wrote:
>>
>> On Thu, Jul 8, 2010 at 03:10, Craig Ringer
>> wrote:
>>>
>>> IIRC on Windows client certificates live in
>>>
>>> %APPDATA%\.postgresq
the best thing would be to store the contents 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 ;)
-
ng an environment variable approach? Sure, please
> propose an exact test, and we'll perform. (No one else here is using certs
> under Windows 7?)
Either environment variable or connection string parameter. See
http://www.postgresql.org/docs/9.0/static/libpq-connect.html, for the
param
,
since you clearly have a working server-side and client-in-java env.
If it doesn't work for you, that's a whole 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
e server actually requests the
cert.. And the API documentation for stat() on windows 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
Website escapes way too much
> Details:
>
> some parts of the website have escaping issues, see
> http://www.postgresql.org/about/featuredetail/feature.189 for an example
Hi!
This is a known issue in the code, and will be fixed in the next
release of the website. Thanks
in
>> the neck.
>
> well that's why we recommend to use the new version of pg_dump to dump the
> old cluster if the intention is an upgrade not sure that is any more pain
> than manually hacking the dump...
yeah. There are (supposedly?) a lot of *other* cases where using an
1 - 100 of 552 matches
Mail list logo
