tons of hits for articles and RDBMS reviews
that mention SuperSmack, but no hits for the actual software.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
.pdf
I believe this is more up to date:
ftp://sqlstandards.org/SC32/WG3/Progression_Documents/FDIS/4FDIS1-02-Foundation-2003.pdf
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
detected in rules for relation test
des=# insert into test ( word ) values ( 'hello' );
ERROR: infinite recursion detected in rules for relation test
any suggestions?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1
Any suggestions?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
Index: src/backend/parser/analyze.c
===
RCS file: /home/pqcvs/pgsql-server/src/backend/parser/analyze.c,v
retrieving revision 1.283
diff -u -u -r1.283 analyze.c
is already in feature freeze, the earliest
opportunity for something like this would be 7.5.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
DES
--
Dag-Erling Smørgrav - d...@des.no
--- src/include/port.h.orig 2009-11-14 16:39:41.0 +0100
+++ src/include/port.h 2010-03-10 13:17:27.0 +0100
@@ -337,6 +337,7 @@
* When necessary, these routines are provided by files in src/port/.
*/
#ifndef HAVE_CRYPT
+#define crypt
Tom Lane t...@sss.pgh.pa.us writes:
Dag-Erling Smørgrav d...@des.no writes:
1. PostgreSQL's private versions of inet_aton etc. can conflict with
similar functions in other libraries (in my case, PostgreSQL's
inet_aton conflicts with libavformat's).
So what? We don't link
Magnus Hagander mag...@hagander.net writes:
Dag-Erling Smørgrav d...@des.no writes:
Your users might need to link with both. I'm working on an
application that generates animations (specifically, animated
weather forecasts) based on data retrieved from a PostgreSQL
database.
This shows
is teach the mingw build path how
to respect the exports list for libpq?
If that works, I'm all for it. I have no idea how to do it, though.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
Tom Lane t...@sss.pgh.pa.us writes:
Dag-Erling Smørgrav d...@des.no writes:
Without this patch, pg_ctl fails to build...
It builds for everybody else (and we do have multiple mingw machines in
the buildfarm, so it's not like this doesn't get tested). I think there
is some other factor
a single C file with some of
the functions declared as static. However, when you do that, you lose
an important advantage of static libraries: the ability to link only
what you need.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
binaries are much easier to distribute, for one;
and there are platforms where shared libraries simply do not exist, or
where the entire system runs in a single namespace. Netware is still
alive and kicking.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql
' # allowed SSL protocols
#ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH' # allowed SSL ciphers
# (change requires restart)
#ssl_renegotiation_limit = 512MB # amount of data between renegotiations
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers
)
will make life much easier for everyone if a POODLE-like vulnerability
is discovered in TLS.
You should as well register your patch to the current commit fest, I
think you are still in time:
https://commitfest.postgresql.org/action/commitfest_view?id=24
Thanks for reminding me.
DES
--
Dag-Erling
will not be vulnerable due to specific details of its
protocol or how it uses TLS, but that's a gamble which you will
eventually lose.
Moreover, the GUC could easily be misused to decrease rather than increase
one's security, if it's carelessly set.
That's the user's responsibility.
DES
--
Dag-Erling
to include the client side.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
* for an application than to explicitly select which
protocols it wants to use (or at least which protocols it wants to
avoid). And you can't change OpenSSL, because a ton of old crappy
software is going to break.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers
is not
present in 1.0 because it involves a specific algorithm or mode that 1.0
does not support.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Magnus Hagander mag...@hagander.net writes:
Yes, it does that. Though it only does it on 9.4,but with the facts we
know now, what 9.4+ does is perfectly safe.
Agreed.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
Martijn van Oosterhout klep...@svana.org writes:
Dag-Erling Smørgrav d...@des.no writes:
If I understand correctly, imaps has been shown to be vulnerable as
well, so I wouldn't be so sure.
Reference?
Sorry, no reference. I was told that Thunderbird was vulnerable to
POODLE when talking
to
backport 1.1 and 1.2 (which I seriously doubt).
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
26c375b6bdefb018b9dd7df463658320
Thus, if you disable all SSL 3.0 ciphers, you also disable TLS 1.0.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
on the libpq side as suggested in the
original discussion might help here.
I can easily do that, but I won't have time until next week or so.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
should reject early.
It's not really early or late, but rather within the loop or at the
end of it. From the users' perspective, the difference is that they
get (to paraphrase) SSLv2 is not allowed instead of syntax error and
that they can use constructs such as ALL:-SSLv2.
DES
--
Dag-Erling
it.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
though,
libpq-openssl.h?
Perhaps ssloptions.[ch], unless you plan to add non-option-related code
there later?
BTW, there is no Regent code in your openssl.c, so the copyright
statement is incorrect.
DES
--
Dag-Erling Smørgrav - d...@des.no
--
Sent via pgsql-hackers mailing list (pgsql-hackers
26 matches
Mail list logo
