On Fri, 13 Jun 2008 16:14:13 -0400 Alvaro Herrera wrote:
Andrew Sullivan wrote:
This is because DNS RRs have a TTL on them, so looking up the host at
any moment other than when you're actually doing the authentication is
prone to error.
Perhaps the solution to this problem is to do
Andrew Dunstan wrote:
OK, I have spent some time generating and filtering typdefs via objdump
on various platforms. I filtered them and Bruce's list to eliminate
items not actually found in the sources thus:
Did this go anywhere?
--
Alvaro Herrera
Alvaro Herrera wrote:
Andrew Dunstan wrote:
OK, I have spent some time generating and filtering typdefs via objdump
on various platforms. I filtered them and Bruce's list to eliminate
items not actually found in the sources thus:
Did this go anywhere?
I'm still trying to
I noticed that typedef Relation *RelationData could be moved to
relcache.h instead of rel.h. This means not #including rel.h in a ton
of header files, instead including just relcache.h. This is a good
thing because relcache.h is a much more lightweight header; rel.h on the
other hand needs quite
Alvaro Herrera wrote:
Perhaps the solution to this problem is to do the lookups and store the
TTL of each answer. At the time of actually checking you need only get
a new answer for those that expired.
Isn't that what a local DNS caching-only server would accomplish?
--
Sent via
Alvaro Herrera [EMAIL PROTECTED] writes:
I noticed that typedef Relation *RelationData could be moved to
relcache.h instead of rel.h.
This seems OK.
While doing that, I noticed that there are some trigger definitions in
rel.h that really belong to trigger.h.
I think you should leave this
Dickson S. Guedes wrote:
SSH uses an approach like that.
It would probably be a good idea to check how other programs deal with
hostname lookups during authentication. Programs like SSH, Apache, and Squid
come to mind.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
David Fetter wrote:
I forgot to post the fact that I'd put up a
http://wiki.postgresql.org/wiki/How_to_sponsor_a_feature, per my
TODO from the developers' meeting in Ottawa.
This describes how to *develop* a feature, not how to *sponsor* it. I don't
think this addresses the issues brought up
Joshua D. Drake wrote:
In reality though, what should happen is we should have a list of
companies and consultants that are willing to be paid to implement
features, todos and bug fixes.
I think the professional support company listing is already that list.
--
Sent via pgsql-hackers mailing
Neil Conway wrote:
There is some precedent for not emitting the messages: most Unix tools
don't echo the results of applying their .rc files at startup.
Unix shells do echo the output generated by the startup files. It's just that
most Unix tools don't generate that much output.
--
Sent via
I was thinking about the proposals that have been made a couple of times
to offer a variant of VACUUM that works by table-rewriting (ie, same as
CLUSTER except for not sorting the rows). I thought I'd do some
experimentation to see what a reasonable syntax for it would be.
I soon convinced
Tom Lane wrote:
maybe it
is time to bite the bullet and clean up VACUUM's syntax so that new
modifiers can be added without making them reserved words. The first
idea that comes to mind is something like
VACUUM [tablename] [ WITH REPLACE, VERBOSE [, ...] ]
I'd be OK with putting
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane wrote:
maybe it
is time to bite the bullet and clean up VACUUM's syntax so that new
modifiers can be added without making them reserved words. The first
idea that comes to mind is something like
I'd be OK with putting the options at the
On Mon, 16 Jun 2008, Peter Eisentraut wrote:
Joshua D. Drake wrote:
In reality though, what should happen is we should have a list of
companies and consultants that are willing to be paid to implement
features, todos and bug fixes.
I think the professional support company listing is already
Greg Smith wrote:
On Mon, 16 Jun 2008, Peter Eisentraut wrote:
Joshua D. Drake wrote:
In reality though, what should happen is we should have a list of
companies and consultants that are willing to be paid to implement
features, todos and bug fixes.
I think the professional support
Buildfarm bobcat is broken running the pltcl regression tests - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=bobcatdt=2008-06-15%2022:43:01
and I have reproduced this on Fedora 9 myself. This distro has Tcl 8.5.1.
I'm not sure exactly what has broken here, but I'm guessing it is
Hi,
we recently try to build a costumer index type around 8.3, for now
want to teach
planner to pick up specific index for our query, so we'd like to use
some document
about how a query tree trun into different query plan and how to
decide which one
to use. Is there any document about
On Mon, 2008-06-16 at 08:59 +0800, laser wrote:
Hi,
we recently try to build a costumer index type around 8.3, for now
want to teach
planner to pick up specific index for our query, so we'd like to use
some document
about how a query tree trun into different query plan and how
Tom Lane [EMAIL PROTECTED] wrote:
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
Postgres 8.4 has pg_stat_user_functions view to track number of calls
of stored functions and time spent in them. Then, I'm thinking a
sql statement version of similar view -- pg_stat_statements.
We don't
Hi.
I'm working on a patch where if you say \ef foo in psql, it'll start
$EDITOR with a CREATE OR REPLACE FUNCTION statement to recreate the
function. So you edit and save and quit, and if you made any changes,
psql will execute the statement.
The psql(/command.c) parts of this are quite simple.
Robert Treat [EMAIL PROTECTED] wrote:
On Friday 13 June 2008 12:58:22 Josh Berkus wrote:
I can see how this would be useful, but I can also see that it could be a
huge performance burden when activated. So it couldn't be part of the
standard statistics collection.
A lower overhead way
On Mon, Jun 16, 2008 at 12:24:28AM +0200, Peter Eisentraut wrote:
David Fetter wrote:
I forgot to post the fact that I'd put up a
http://wiki.postgresql.org/wiki/How_to_sponsor_a_feature, per my
TODO from the developers' meeting in Ottawa.
This describes how to *develop* a feature, not
Andrew Dunstan [EMAIL PROTECTED] writes:
Buildfarm bobcat is broken running the pltcl regression tests - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=bobcatdt=2008-06-15%2022:43:01
and I have reproduced this on Fedora 9 myself. This distro has Tcl 8.5.1.
I missed 8.5.1, but I can say
I understand there must be some overhead because we're collecting
extra info. I'm curious if there're considerable amount of overhead
to the users who don't want such additional trance.
2008/6/16 ITAGAKI Takahiro [EMAIL PROTECTED]:
Robert Treat [EMAIL PROTECTED] wrote:
On Friday 13 June
Peter Eisentraut wrote:
Joshua D. Drake wrote:
In reality though, what should happen is we should have a list of
companies and consultants that are willing to be paid to implement
features, todos and bug fixes.
I think the professional support company listing is already that list.
Andrew Dunstan wrote:
Plus an ability to filter the list on those criteria. I'd also like to
see a space for companies to state which PostgreSQL major contributors
are working for them. That should be of some assistance to sponsors in
picking a development company to deal with.
+1
Joshua
Abhijit Menon-Sen [EMAIL PROTECTED] writes:
The problem is, of course, generating the CREATE OR REPLACE statement.
There is some code to do this in pg_dump.c:dumpFunc(), but it's strongly
tied to pg_dump (global variables, output to Archive *, dependencies on
other functions, etc.).
I could
On Mon, 16 Jun 2008, Peter Eisentraut wrote:
David Fetter wrote:
I forgot to post the fact that I'd put up a
http://wiki.postgresql.org/wiki/How_to_sponsor_a_feature, per my
TODO from the developers' meeting in Ottawa.
This describes how to *develop* a feature, not how to *sponsor* it. I
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Buildfarm bobcat is broken running the pltcl regression tests - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=bobcatdt=2008-06-15%2022:43:01
and I have reproduced this on Fedora 9 myself. This distro has Tcl 8.5.1.
I
At 2008-06-15 23:35:34 -0400, [EMAIL PROTECTED] wrote:
There's been a lot of talk (but no action) about refactoring pg_dump
into a library plus wrapper.
Yes. After having tried to do what would have amounted to just a small
part of that work, I can see why nobody has done it yet.
I'd much
On Fri, 2008-06-13 at 22:38 -0400, Andrew Sullivan wrote:
If you don't look up
at _least_ at connection time, this feature should be rejected on the
grounds that it opens a new authentication hole a mile wide.
That seems conclusive to me.
--
Simon Riggs www.2ndQuadrant.com
Hi,
On Sun, 2008-06-15 at 20:54 -0400, Andrew Dunstan wrote:
Has anyone been able to get the tests to pass using Tcl 8.5.1?
All regression tests passed on Fedora-9 while building new RPM sets.
Regards,
--
Devrim GÜNDÜZ , RHCE
PostgreSQL Replication, Consulting, Custom Development, 24x7
Howdy,
Possibly showing my ignorance here, but as I'm working on updating
citext to be locale-aware and to work on 8.3, I've run into this
peculiarity:
try=# \encoding
UTF8
try=# select setting from pg_settings where name = 'lc_collate';
setting
-
en_US.UTF-8
(1 row)
try=#
33 matches
Mail list logo
