is that an uninformed application might take the wrong locks, and
bollix up your intended usage accidentally.
This sounds like one more attempt to protect against idiots, which universe
tend to produce on a pretty quick rate :)
My 2¢,
--
Dimitri Fontaine
Directeur Technique
Tel: 06 74 15 56 53
Le jeudi 04 septembre 2008, Robert Treat a écrit :
To paraphrase, if you can't write a config file correctly before
restarting, I do not want you anywhere near any instance of a production
system
Do you really want to TCO of PostgreSQL to raise that much when the software
could help lowering
messaging, now it has
been reworked to follow your advices, could be of some use here?
http://archives.postgresql.org/pgsql-hackers/2008-07/msg01114.php
http://archives.postgresql.org/pgsql-hackers/2008-07/msg01420.php
Regards,
- --
dim
- --
Dimitri Fontaine
PostgreSQL DBA, Architecte
Hi,
Le mardi 09 septembre 2008, Heikki Linnakangas a écrit :
The tricky part is, how does A know if it should wait, and for how long?
commit_delay sure isn't ideal, but AFAICS the log shipping proposal
doesn't provide any solution to that.
It might just be I'm not understanding what it's all
Le mardi 09 septembre 2008, Markus Wanner a écrit :
..and it will still has to wait until WAL is written to disk on the
local node, as we do now. These are two different things to wait for.
One is a network socket operation, the other is an fsync(). As these
don't work together too well
Le mardi 09 septembre 2008, Simon Riggs a écrit :
If the WALWriter|Sender is available, it can begin the task immediately.
There is no need for it to wait if you want synchronous behaviour.
Ok. Now I'm as lost as anyone with respect to how you get Group Commit :)
--
dim
signature.asc
Hi,
Le mercredi 10 septembre 2008, Heikki Linnakangas a écrit :
Sure. That's the fundamental problem with synchronous replication.
That's why many people choose asynchronous replication instead. Clearly
at some point you'll want to give up and continue without the slave, or
kill the master
Le jeudi 11 septembre 2008, Heikki Linnakangas a écrit :
Well, yes, but you can fall behind indefinitely that way. Imagine that
each transaction on the slave lasts, say 10 minutes, with a new
transaction starting every 5 minutes. On the master, there's a table
that's being vacuumed (or
Le jeudi 11 septembre 2008, Csaba Nagy a écrit :
Well now that I think I understand what Heikki meant, I also think the
problem is that there's no choice at all to advance, because the new
queries will simply have the same snapshot as currently running ones as
long as WAL reply is blocked...
Le jeudi 18 septembre 2008, David E. Wheeler a écrit :
So I'm wondering, given the various discussions of PostgreSQL module
hosting in the past, where would be a good place to put a PostgreSQL
module project? The things I would like to have are:
* SVN or git hosting (I've not used git, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Le 20 sept. 08 à 09:42, Dave Page a écrit :
On Sat, Sep 20, 2008 at 8:37 AM, Joshua D. Drake
[EMAIL PROTECTED] wrote:
Dave Page wrote:
Well that's not strictly true - I persuaded one of the GForge
developers to work on the upgrade. As far
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Who can resist the programming language game?
Le 19 sept. 08 à 22:37, D'Arcy J.M. Cain a écrit :
On Fri, 19 Sep 2008 20:57:36 +0100
Dave Page [EMAIL PROTECTED] wrote:
On Fri, Sep 19, 2008 at 8:54 PM, Gevik Babakhani [EMAIL PROTECTED]
wrote:
Le lundi 22 septembre 2008, Andrew Dunstan a écrit :
You'd really want the latter anyway for some cases, ie, when you don't
want the restore trying to hog the machine. Maybe the right form for
the extra option is just a limit on how many connections to use. Set it
to one to force the
Le lundi 22 septembre 2008, Joshua Drake a écrit :
I will not argue vehemently here but I will say that jobs doesn't
seem correct. The term workers seems more appropriate.
Mmmm, it sounds like it depends on the implementation (and how all workers
will share the same serializable transaction or
Hi,
Le mardi 23 septembre 2008, Andrew Dunstan a écrit :
In any case, my agenda goes something like this:
* get it working with a basic selection algorithm on Unix (nearly
done - keep your eyes open for a patch soon)
* start testing
* get it working on Windows
*
Le mercredi 24 septembre 2008, Andrew Dunstan a écrit :
No. The proposal will perform exactly the same set of steps as
single-threaded pg_restore, but in parallel. The individual steps won't
be broken up.
Ok, good for a solid trustworthy parallelism restore. Which is exactly what we
want.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 24 sept. 08 à 18:56, Andrew Dunstan a écrit :
The is purely a patch to pg_restore. No backend changes at all (and
if I did it would not use anything that isn't in core anyway).
Ok, good.
I'm eager to see what -core hackers will want to do with
Le lundi 29 septembre 2008, Tom Lane a écrit :
* Extend the archive format to provide some indication that restoring
this object requires exclusive access to these dependencies.
* Hardwire knowledge into pg_restore that certain types of objects
require exclusive access to their dependencies.
Hi,
Le mardi 30 septembre 2008, Heikki Linnakangas a écrit :
pg_relation_size() doesn't include the size of the FSM. Should it? I'm
thinking no, but pg_total_relation_size() should.
What's practical about pg_relation_size() and pg_total_relation_size() as of
8.3 is that the diff is the
Le mardi 30 septembre 2008, Heikki Linnakangas a écrit :
Dimitri Fontaine wrote:
Question for the slow readers: this new FSM scheme being dynamic, it's no
longer possible to have table bloat, right?
(where table bloat is full of dead-for-any-transaction tuples, and you
have to CLUSTER
Le mardi 30 septembre 2008, Heikki Linnakangas a écrit :
You forgot the toast size.
Yeah, pg_total_relation_size() - pg_relation_size() is not equal to the
total size of indexes because of that.
Oops. Thanks for pointing this to me...
But you can do SUM(pg_relation_size(index)) across all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Le 30 sept. 08 à 20:03, Tom Lane a écrit :
set_read_position(tupstore, local_read_position);
tuple = tuplestore_gettuple(tupstore, ...);
get_read_position(tupstore, local_read_position);
rather than just
Le jeudi 02 octobre 2008, Heikki Linnakangas a écrit :
pg_relation_size('footable') for size of the main data fork
pg_relation_size('footable', 'fsm') for FSM size
As good as possible, if you ask me!
Regards,
--
dim
signature.asc
Description: This is a digitally signed message part.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Le 11 oct. 08 à 01:50, Tom Lane a écrit :
Alvaro Herrera [EMAIL PROTECTED] writes:
It seems that the real way forward is to improve on that patch.
Yeah. If the schema-per-module answer were really a good answer,
we'd have done it before
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Le 11 oct. 08 à 21:10, Josh Berkus a écrit :
Am I correct in assuming, however, that you're not at all likely to
complete this for 8.4?
Not only that, but as I've yet to discover PostgreSQL internal code,
it would ask a lot of help and
Le jeudi 23 octobre 2008, Tom Lane a écrit :
Peter Eisentraut [EMAIL PROTECTED] writes:
It turns out you cannot EXPLAIN on CREATE TABLE AS, but it seems to work
fine if I extend the grammar as below:
This seems to me to be something that will look like a wart, not a
feature, from the
Hi,
In the python language, functions that lazily return collections are called
generators and use the yield keyword instead of return.
http://www.python.org/doc/2.5.2/tut/node11.html#SECTION0011100
Maybe having such a concept in PostgreSQL would allow the user to choose
Le mardi 28 octobre 2008, Pavel Stehule a écrit :
2008/10/28 Dimitri Fontaine [EMAIL PROTECTED]:
Hi,
In the python language, functions that lazily return collections are
called generators and use the yield keyword instead of return.
http://www.python.org/doc/2.5.2/tut/node11.html
Le mercredi 29 octobre 2008, Tom Lane a écrit :
So the fact that it's possible for SQL-language functions is an
idiosyncrasy of that language, not something we should cram into the
general CREATE FUNCTION syntax in the vain hope that having syntax
might cause an implementation to appear
Le mercredi 29 octobre 2008, Tom Lane a écrit :
Well, call-per-value is *necessary* for lazy evaluation, but it's not
*sufficient*. You need a function implementation that can suspend and
resume execution, and that's difficult in general.
Ok, I think I begin to understand how things are tied
Le mercredi 29 octobre 2008, Tom Lane a écrit :
Now of course the bigger problem with either this syntax or yours is
that attaching such a property to a function is arguably the Wrong Thing
in the first place. Which one is the best way is likely to depend on
the calling query more than it
Le vendredi 31 octobre 2008, Tom Lane a écrit :
With the attached patch, SQL functions support returning the results of
INSERT/UPDATE/DELETE RETURNING clauses.
Thanks for your work and for having considered user whining in-passing! :)
--
dim
signature.asc
Description: This is a digitally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Le 25 nov. 08 à 20:29, Ron Mayer a écrit :
psql=# install module sampledb;
Downloading sampledb from pgfoundry...
Installing sampledb
Connecting to sampledb
sampledb=#
This could be part of an installer for PostgreSQL extensions. See
Hi,
Le mercredi 26 novembre 2008, Tom Lane a écrit :
You might want to pull the diffs for some past pg_proc addition from
CVS and go over the changes. This one is a good minimal example:
http://archives.postgresql.org/pgsql-committers/2005-03/msg00433.php
The following link should help the
Hi,
I hope I'm not disturbing hackers at work by talking about completely
unrelated things but...
Le mardi 09 décembre 2008, Tom Lane a écrit :
I think we need something closer to the postmaster signal multiplexing
mechanism, wherein there is a dedicated shared memory area of static
layout
Hi,
Pavel Stehule pavel.steh...@gmail.com writes:
I am sending actualised patch.
I've volunteered to review this patch, and before getting to read code
and documentation, then to test it, I have some more general question.
The idea to add support for typmods in function signatures came from
Le 17 nov. 2009 à 20:33, Tom Lane a écrit :
We could to talk about it now. We are not hurry. But I would to see
some progress in this area in next two months. This patch is simple
and doesn't create any new rules or doesn't change behave.
What do you mean it doesn't change the behavior? It
Robert Haas robertmh...@gmail.com writes:
Forgive me if this is discussed before, but why does this store the
strategy numbers of the relevant operators instead of the operators
themselves? It seems like this could lead to surprising behavior if
the user modifies the definition of the
Hi,
Le 29 nov. 2009 à 18:22, Tom Lane a écrit :
I think we should use GUC_NO_RESET_ALL.
I agree with you, but it seems we have at least as many votes to not do
that. Any other votes out there?
Driven by the pooler use case (pgbouncer, even), I'd say RESET ALL should reset
also the
Le 30 nov. 2009 à 00:25, Tom Lane a écrit :
The thing is that the libpq API treats application_name as a *property
of the connection*.
Oh. Yeah.
We could add a third keyword, say SET DEFAULT, that would have the
behavior of setting the value in a fashion that would persist across
resets.
Le 30 nov. 2009 à 22:38, Robert Haas a écrit :
I still don't really understand why we wouldn't want RESET ALL to
reset the application name. In what circumstances would you want the
application name to stay the same across a RESET ALL?
I can't see any use case, but SET/RESET is tied to
Hi,
As we're talking about crazy ideas...
Bruce Momjian br...@momjian.us writes:
Well, yea, the idea would be that the 8.5 server would either convert
the page to the new format on read (assuming there is enough free space,
perhaps requiring a pre-upgrade script), or have the server write the
Greg Stark gsst...@mit.edu writes:
On Wed, Dec 2, 2009 at 11:26 AM, Dimitri Fontaine
dfonta...@hi-media.com wrote:
We already have had demand for read only tables (some on-disk format
optimisation would then be possible). What about having page level
read-only restriction, thus allowing
Le 4 déc. 2009 à 20:40, Tim Bunce a écrit :
Robert's comparison with mod_perl is very apt. Preloading code gives
dramatic performance gains in production situations where there's a
significant codebase and connections are frequent.
How far do you go with using a connection pooler such as
Le 6 déc. 2009 à 23:26, Robert Haas a écrit :
Consider this scenario:
0. You have a master and a standby configured properly, and up and running.
1. You shut down master for some reason.
2. You restart standby. For some reason. Maybe by accident, or you want
to upgrade minor version or
Hi,
Greg Smith g...@2ndquadrant.com writes:
Robert Haas wrote:
The main point here for me is that the JSON format is already
parseable by YAML parsers, and can probably be turned into YAML using
a very short Perl script - possibly even using a sed script. I think
that it's overkill to
Tom Lane t...@sss.pgh.pa.us writes:
Right, just like every other thing that's pre-installed. If a
particular installation wishes to let individual DB owners control this,
the superuser can drop plpgsql from template1. It's not apparent to me
why we need to allow non-superusers to override
Tom Lane t...@sss.pgh.pa.us writes:
Why not? If they really want to prohibit use of a feature the upstream
project has decided should be standard, that's their privilege.
Well, I guess they could also automate their database creation to fix
the privileges and assign the ownership of the
Tom Lane t...@sss.pgh.pa.us writes:
It's not impossible that we'll have to tweak pg_dump a bit; it's
never had to deal with languages that shouldn't be dumped ...
Ah, the best would be to have extensions maybe. Then you could do this
in initdb, filling in template0:
CREATE EXTENSION plpgsql
Hi,
Le 11 déc. 2009 à 01:43, Bruce Momjian a écrit :
Would you be up for writing the extension facility?
Uh, well, I need to help with the patch commit process at this point ---
if I find I have extra time, I could do it. I will keep this in mind.
If you ever find the time to do it, that
Le 13 déc. 2009 à 19:48, Magnus Hagander a écrit :
The buildscript that's there can generate buildfiles for contrib. I
haven't used it to build external contrib modules, but it's probably
a pretty good start. If not, just steal the project file from another
contrib module and modify the files
Scott Bailey arta...@comcast.net writes:
So basically I have an anyrange pseudo type with the functions prev, next,
last, etc defined. So instead of hard coding range types, we would allow the
user to define their own range types. Basically if we are able to determine
the previous and next
Tom Lane t...@sss.pgh.pa.us writes:
foreach p2_member in unnest(p2) loop
p1 := array(select period_except(p1_member, p2_member)
from unnest(p1) p1_member);
end loop;
But maybe it can be done in a single SQL command.
Yeah, as soon as you have LATERAL,
Tom Lane t...@sss.pgh.pa.us writes:
Dimitri Fontaine dfonta...@hi-media.com writes:
Tom Lane t...@sss.pgh.pa.us writes:
foreach p2_member in unnest(p2) loop
p1 := array(select period_except(p1_member, p2_member)
from unnest(p1) p1_member);
end loop
Hi,
Le 17 déc. 2009 à 19:39, Josh Berkus a écrit :
Mind you, returning (arbitrary expression) would be even better, but if
we can get returning TEXT[] for 8.5, I think it's worth doing on its own.
Well, you already have it as soon as you have text[]:
INSERT INTO destination
SELECT row[0],
Hi,
Le 18 déc. 2009 à 19:21, Heikki Linnakangas a écrit :
On Fri, Dec 18, 2009 at 12:22 PM, Florian Pflug fgp.phlo@gmail.com
wrote:
It'd prefer if the slave could automatically fetch a new base backup if it
falls behind too far to catch up with the available logs. That way, old logs
Le 19 déc. 2009 à 03:01, Robert Haas a écrit :
On Fri, Dec 18, 2009 at 8:32 PM, Simon Riggs sri...@postgresql.org wrote:
Log Message:
---
Allow read only connections during recovery, known as Hot Standby.
Congratulations! And, may I be the first to say - woo hoo!
+1!
--
dim
--
Hi from a real user :)
Le 20 déc. 2009 à 22:08, Tom Lane a écrit :
Pavel Stehule pavel.steh...@gmail.com writes:
b) general support for preordered aggregates.
I think that we've already expanded the capabilities of aggregates
a great deal for 8.5, and we should let it sit as-is for a
Hi, sorry for posting style,
--
dim
Le 23 déc. 2009 à 23:58, Jeff Davis pg...@j-davis.com a écrit :
Honestly, I've never used LIKE in a table definition aside from one-
off
design experiments. For that kind of thing, what I want is to just get
everything (except perhaps FKs if the above
Hi,
Le 28 déc. 2009 à 21:33, Kevin Grittner a écrit :
We often see posts from people who have more active connections than
is efficient.
How would your proposal better solve the problem than using pgbouncer?
mad proposal time
I'd be in favor of considering how to get pgbouncer into -core, and
Le 28 déc. 2009 à 22:46, Andres Freund a écrit :
mad proposal time
I'd be in favor of considering how to get pgbouncer into -core, and now
that we have Hot Standby maybe implement a mode in which as soon as a
real XID is needed, or maybe upon receiving start transaction read write
command,
Le 28 déc. 2009 à 22:59, Kevin Grittner a écrit :
With my current knowledge of pgbouncer I can't answer that
definitively; but *if* pgbouncer, when configured for transaction
pooling, can queue new transaction requests until a connection is
free, then the differences would be:
It does that,
Le 28 déc. 2009 à 23:35, Kevin Grittner a écrit :
So the application would need to open and close a pgbouncer
connection for each database transaction in order to share the
backend properly?
No, in session pooling you get the same backend connection for the entire
pgbouncer connection, it's a
Le 28 déc. 2009 à 23:56, Kevin Grittner a écrit :
http://preprepare.projects.postgresql.org/README.html
I just reviewed the documentation for preprepare -- I can see a use
case for that, but I really don't think it has a huge overlap with
my point. The parsing and planning mentioned in my
Tom Lane t...@sss.pgh.pa.us writes:
Actually, in the problematic cases, it's interesting to consider the
following strategy: when scalarineqsel notices that it's being asked for
a range estimate that's outside the current histogram bounds, first try
to obtain the actual current max() or min()
Andrew Dunstan and...@dunslane.net writes:
Does anyone have any real-world experience with any of the JSON C libraries?
I do not, but I see that YAJL http://lloyd.github.com/yajl/ is now in
Fedora, and has a BSDish license
It's there in debian too, unstable and testing, and should be there on
Sergej Galkin sergej.gal...@gmail.com writes:
I realized my own gist index, and now I want to debug it :)
I used Gevel for that:
http://www.sai.msu.su/~megera/wiki/Gevel
Regards,
--
dim
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Robert Haas robertmh...@gmail.com writes:
I think what we should do is either (1) implement a poor man's caching
that doesn't try to cope with any of these issues, and document that
you get what you pay for or (2) reject this idea in its entirety.
Trying to reimplement all of our normal
Kevin Grittner kevin.gritt...@wicourts.gov writes:
I've read through some git tutorials, but
there's a lot to digest and I'm not entirely sure this is a good way
to proceed.
I found that the following video is really helpful at grasping the
concepts of git, that it exposes pretty directly even
Robert Haas robertmh...@gmail.com writes:
If we're going to use a bug-tracker, Bugzilla wouldn't be my first
choice, I don't think. Honestly what I'd like better than a
full-fledged trackers is just a webapp that lists all the unreplied-to
emails in the pgsql-bugs archives.
For something
Dave Page dp...@pgadmin.org writes:
We have discussed this sort of facility at previous developer
meetings, and as I recall came to the conclusion that we need to have
the ability to distribute pre-built binaries, not just source code as
virtually no Windows users are ever going to have a
Robert Haas robertmh...@gmail.com writes:
Hmm. There's something to what you say, but what about the people who
were expecting their patches to be reviewed and perhaps committed in
the forthcoming CommitFest. I proposed a schedule for this release
that involved only three CommitFests and it
Tom Lane t...@sss.pgh.pa.us writes:
No, I don't think so. HS without SR means you still have to fool with
setting up WAL-file-based replication, which despite the existence of
pg_standby is a PITA. And you have to make a tradeoff of how often to
flush WAL files to the standby. To be a real
David E. Wheeler da...@kineticode.com writes:
On Jan 7, 2010, at 2:11 PM, Peter Eisentraut wrote:
You might want to clarify in your prose what an extension is. I
suspect I know what you mean, but perhaps not everyone does.
Good suggestion, thanks. How about this in the FAQ?
* WTF is an
Dimitri Fontaine dfonta...@hi-media.com writes:
e.g. pg_execute_commands_from_file('path/ to/file.sql'). It would not
[...]
Then you need to add a catalog for holding the extensions metadata, like
[...]
Now you can hack a CREATE EXTENSION command to fill-in the catalog, and
the commands
David Fetter da...@fetter.org writes:
If we *must* have SR and it's not in by the 15th, let's do another
Commitfest rather than jack the people who played by the rules.
If we do add another Commitfest what we do is exactly jacking people who
played by the rules. Because all those patches that
Magnus Hagander mag...@hagander.net writes:
Why we can do it this way is because we're not starving on
reviewers. We're starving on commiters time. And seeing this:
Well, we're actually somewhat starving on senior reviewers as well.
That can take on things like the index patches, Writable CTE
Alvaro Herrera alvhe...@commandprompt.com writes:
Leonardo F wrote:
How can I keep up with who's doing what?
Read this list and pgsql-committers.
Or subscribe to the RSS feed from:
http://git.postgresql.org/gitweb?p=postgresql.git;a=summary
--
dim
--
Sent via pgsql-hackers mailing list
Robert Haas robertmh...@gmail.com writes:
I have always
felt that the purpose of a CommitFest was to give everyone a fair
shake at getting their patch reviewed, provided that they followed
certain ground rules.
Yes, like for example submitting the patch before the commit fest
begins.
And
Robert Haas robertmh...@gmail.com writes:
Basically, here's my feeling. Either we have a rule that we can
bounce large, previously-unseen patches from the final CommitFest of
the release cycle, or we don't. If we do, then we should go ahead and
do it, and we should do it early when it will
Congratulations, good things to all the family!
Devrim GÜNDÜZ dev...@gunduz.org writes:
Alvaro, one of our hackers and committers and my colleague more than 4
years, had a new baby today.
Congrats Alvaro for his second daughter !
-committers, please commit your patches for our new
Andrew Dunstan and...@dunslane.net writes:
That is assuming that the MUA gives you the option of specifying the
attachment MIME type. Many (including mine) do not. It would mean an extra
step - I'd have to gzip each patch or something like that. That would be
unfortunate,as well as imposing
Hi,
Another occasion to show ignorance, I couldn't resist!
Tom Lane t...@sss.pgh.pa.us writes:
What you're
talking about would require a great deal more maintenance effort, and
I don't see the point compared to using a VPATH build.
I've discovered VPATH builds pretty recently, in the
Alvaro Herrera alvhe...@commandprompt.com writes:
Absolutely. The month boundary problem boils down to the fact that
Mhonarc does not scale very well, so we can't have mboxes that are too
large. This is why most people split their archives per month, and then
each month is published as an
Magnus Hagander mag...@hagander.net writes:
As for AOX, my understanding is that it is no longer maintained, so
I'd be worried about choosing such a solution for a complex problem.
But it's open for discussion.
Ouch.
--
dim
--
Sent via pgsql-hackers mailing list
Dave Page dp...@pgadmin.org writes:
I recall having tried AOX a long time ago but I can't remember the reason
why I was not satisfied. I guess I can give another try by setting up a test
ML archive.
I tried it too, before I started writing the new prototype archiver
from scratch. I too
Dimitri Fontaine dfonta...@hi-media.com writes:
Magnus Hagander mag...@hagander.net writes:
As for AOX, my understanding is that it is no longer maintained, so
I'd be worried about choosing such a solution for a complex problem.
But it's open for discussion.
Ouch.
It seems that the company
Hi,
The topic came on IRC and it might be that the later attempts at using
another library missed one of the offering, namely FastLZ. It's made for
being quick rather than minimize size, it's MIT licenced, 551 lines of
portable ansi-C code, already tested on a host of systems and compilers.
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Are the concerns from previous discussions off-base?
http://archives.postgresql.org/pgsql-performance/2009-08/msg00053.php
I knew I was forgetting about something, thanks for the reminder. Damn
it, patents.
--
dim
--
Sent via
Dave Page dp...@pgadmin.org writes:
2010/1/12 Matteo Beccati p...@beccati.com:
So, I've decided to spend a bit more time on this and here is a proof of
concept web app that displays mailing list archives reading from the AOX
database:
http://archives.beccati.org/
Seems to work.
Hehe,
Robert Haas robertmh...@gmail.com writes:
I agree. My main concern in terms of dealing with these outstanding
is that it will distract us, particularly Tom, from stabilizing the
tree, especially HS, VF, and SR. If the tree were in a releasable
state today I wouldn't be worrying about it.
Aidan Van Dyk ai...@highrise.ca writes:
I'll note that the whole idea of a email archive interface might be a
very good advocacy project as well. AOX might not be a perfect fit,
but it could be a good learning experience... Really, all the PG mail
archives need is:
1) A nice normalized DB
Aidan Van Dyk ai...@highrise.ca writes:
aox has that either as a bulk importer or as a MDA.
Yup, LMTP is ideally suited for that too.
Yes.
3) A nice set of SQL queries to return message, parts, threads,
folders based on $criteria (search, id, folder, etc)
I guess Matteo's working on
Peter Eisentraut pete...@gmx.net writes:
I was surprised/annoyed to find out that there is no way to have
per-user pg_service.conf, something like ~/.pg_service.conf (well,
except by export PGSYSCONFDIR). That would be easy to add. Comments?
+1.
I'll use it the day it exists.
--
dim
--
Sergej Galkin sergej.gal...@gmail.com writes:
I am realizing gist index and get a bug, that crashes DB. I' debugged
my program as Robert(thanks !) advised me and I know which procedure
crashed.
Using gdb you should have the line number in the source code and should
be able to look up the
Matteo Beccati p...@beccati.com writes:
I've extended AOX with a trigger that takes care of filling a separate table
that's used to display the index pages. The new table also stores threading
information (standard headers + Exchange headers support) and whether or not
the email has
Michael Meskes mes...@postgresql.org writes:
On Wed, Jan 13, 2010 at 10:30:32PM +0100, Hans-Juergen Schoenig wrote:
performance tune your precompiler application. in PostgreSQL it is
currently a little hard to get from the log what is executed how
often by which application in which speed and
Matteo Beccati p...@beccati.com writes:
WITH RECURSIVE t (mailbox, uid, date, subject, sender, has_attachments,
parent_uid, idx, depth) AS (
SELECT mailbox, uid, date, subject, sender, has_attachments, parent_uid,
uid::text, 1
FROM arc_messages
WHERE parent_uid IS NULL AND mailbox = 15
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
If we don't fix that within the server, we will need to document that
caveat and every installation will need to work around that one way or
another. Maybe with some monitoring software and an automatic restart. Ugh.
I wasn't
Tom Lane t...@sss.pgh.pa.us writes:
This works well enough for regular DML statements, but it falls down for
EXPLAIN which is a utility statement, because *parse analysis of utility
statements doesn't do anything*. EXPLAIN actually does the parse
analysis of its contained statement at the
1 - 100 of 1916 matches
Mail list logo
