On Feb 22, 2010, at 12:25 PM, Tom Lane wrote:
I think we already missed the window where it would have been sensible
to install a hack workaround for this. If we'd done that in November
it might have been reasonable, but by now it's too late for any hack
we install to spread much faster than
On Feb 3, 2010, at 10:16 AM, Stefan Kaltenbrunner wrote:
Robert Haas wrote:
On Wed, Feb 3, 2010 at 6:24 AM, Chris Campbell chris_campb...@mac.com
wrote:
The flurry of patches that vendors have recently been making to OpenSSL to
address
the potential man-in-the-middle attack during SSL
Greetings, hackers!
The flurry of patches that vendors have recently been making to OpenSSL to
address the potential man-in-the-middle attack during SSL renegotiation have
disabled SSL renegotiation altogether in the OpenSSL libraries. Applications
that make use of SSL renegotiation, such as
Is there a way to detect when the SSL library has renegotiation disabled?
(Either at compile-time or runtime, although runtime would definitely be better
because we’ll change our behavior if/when the user updates their SSL library.)
If so, we could skip renegotiation when it’s disabled in the
We're getting deadlock error messages in the production database logs
during times of inactivity, where the only other thing using the
database (we think) is the every-15-minutes pg_dump process. There
are still database connections up-and-running from unused Hibernate
Java processes, but
On Oct 26, 2006, at 17:21, Tom Lane wrote:
And what was 1171 doing? I really doubt that either of these could
have
been pg_dump.
I know that process 1120 is a Java client (Hibernate) running an
UPDATE query, but I have no idea what 1171 is. I doubt that 1171 was
pg_dump, but when we
On Oct 26, 2006, at 18:45, Tom Lane wrote:
log_min_error_statement = error would at least get you the statements
reporting the deadlocks, though not what they're conflicting against.
Would it be possible (in 8.3, say) to log the conflicting backend's
current statement (from
On Oct 17, 2006, at 15:19, Peter Eisentraut wrote:
Mark Woodward wrote:
Shouldn't this work?
select ycis_id, min(tindex), avg(tindex) from y where ycis_id = 15;
ERROR: column y.ycis_id must appear in the GROUP BY clause or be
used in an aggregate function
This would require a great deal
On Oct 8, 2006, at 14:29, Tom Lane wrote:
Looks good, but I don't think we want to abandon OSX 10.2 support
just yet. I'll revise this to use a configure probe for dlopen.
Maybe we can abandon Mac OS X 10.2 in 8.3 and later? And not back-
port these patches to the 7.x, 8.0, and 8.1
I've grepped through the source code, and the only thing I can find
that uses readline (or libedit) is psql.
Is that correct?
If that's the case, how hard would it be to link only psql with
readline (or libedit)?
Currently, if you ./configure with readline support, -lreadine (or -
ledit)
The documentation [1] says this about On-line backup and point-in-
time recovery:
If we continuously feed the series of WAL files to another machine
that has been loaded with the same base backup file, we have a hot
standby system: at any point we can bring up the second machine
and it
On Jul 5, 2006, at 14:51, Phil Frost wrote:
test=# create function bump() returns bigint language sql security
definer as $$ select nextval('private.seq'); $$;
SECURITY DEFINER means that the function runs with the permissions of
the role used to create the function (ran the CREATE
I heard an interesting feature request today: preventing the
execution of a DELETE or UPDATE query that does not have a WHERE clause.
The user was worried about a typo leading to:
DELETE FROM very_important_table
and deleting all the data. Or doing something similar with an UPDATE:
On Feb 3, 2006, at 02:09, Tino Wildenhain wrote:
Well if the view does not suit your needs, why dont you use an
set returnung function instead? Inside it you can do all the magic
you want and still use it similar to a table or view.
That's what I'm currently doing (as explained in the first
On Feb 3, 2006, at 08:50, Martijn van Oosterhout wrote:
Hmm, we actually do inline SQL functions under certain situations, but
only for simple queries (see inline_function in
optimizer/util/clauses.c). One approach would be to expand that
function to inline more complicated things.
* Better
On Feb 3, 2006, at 10:25, Martijn van Oosterhout wrote:
Sure, for most procedural languages you can't do much. But we do do
syntax checking already and checking that the necessary functions
exist
can be considered part of that. It' s not terribly important though.
Dependancy tracking needs
On Feb 3, 2006, at 12:43, Rick Gigger wrote:
If he had multiple ips couldn't he just make them all listen only
on one specific ip (instead of '*') and just use the default port?
Yeah, but the main idea here is that you could use ipfw to forward
connections *to other hosts* if you wanted
On Feb 3, 2006, at 12:27, Tom Lane wrote:
I guess I can live without the dependancy tracking. I can always dump
and reload my database to re-parse all the functions. Maybe we could
have a RELOAD FUNCTION command that would just re-parse an existing
function, so I don't have to dump and reload?
On Feb 3, 2006, at 11:21, Tom Lane wrote:
The SRF concept captures what you want a whole lot better. If the
implementation isn't up to snuff, we should improve it, not warp other
pieces of the system.
Point taken. The rewriting concept is what I'm after; if that can be
done pre-planning
I've written some complicated queries that I'd like to save inside
the server and then call from my clients using a short name. For the
queries that require no external information, views are perfect. For
queries that *do* require external information (like a search date
range), I've used
On Feb 2, 2006, at 23:33, Greg Stark wrote:
The right way to go about this in the original abstract set-
theoretic
mindset of SQL is to code the view to retrieve all the rows and
then apply
further WHERE clause restrictions to the results of the view.
So for example this:
CREATE VIEW
On Jun 22, 2005, at 12:52, Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
Is there a way to confirm which libpq.so psql and/or dblink.so has
linked to? Are there any other tests I could run to shed some
light on
this?
On Linux you use ldd to find out what the linker will do with
I think we should add a new wal_sync_method that will use Darwin's
F_FULLFSYNC fcntl().
From sys/fnctl.h:
#define F_FULLFSYNC 51 /* fsync + ask the drive to
flush to the media */
This fcntl() will basically perform an fsync() on the file, then flush
the write cache of the
Harald Fuchs wrote:
Why don't you just do
( echo -- This is my comment
pg_dump whatever
) dumpfile
?
How could I dump using the custom format, and then use dumpfile with
pg_restore to restore the dump? If I just prepend the comment to the
file, then pg_restore will choke, since the file
I've encountered a situation where I'd like to store some information
about the database when I do a pg_dump. For instance, the timestamp of
the dump. And some other information that I pull from the database.
If pg_dump had a --comment flag that allowed me to pass a string that
would be stored
25 matches
Mail list logo
