[EMAIL PROTECTED] (Andrew Dunstan) writes:
A.M. wrote:
Speaking of language choice, no one said that _all_ the source code
would need to be rewritten. It would be nice, for example, if
PostgreSQL rewrote the current GUC system with a glue language like
Lua (which is also very C-like).
No it
[EMAIL PROTECTED] (Jonah H. Harris) writes:
On Fri, Sep 26, 2008 at 11:52 AM, Andrew Dunstan [EMAIL PROTECTED] wrote:
Speaking of language choice, no one said that _all_ the source code would
need to be rewritten. It would be nice, for example, if PostgreSQL rewrote
the current GUC system with
[EMAIL PROTECTED] (Martin Pihlak) writes:
Tons of details have been omitted, but should be enough to start discussion.
What do you think, does this sound usable? Suggestions, objections?
Slony-I does some vaguely similar stuff in its handling of connection paths;
here's the schema:
create
[EMAIL PROTECTED] (Jonah H. Harris) writes:
On Sun, Nov 9, 2008 at 7:41 PM, Decibel! [EMAIL PROTECTED] wrote:
I think you're barking up the wrong tree here; the community can't really do
hacking for hire. If you want to pay for something to be implemented (which
is great!), you'll need to talk
[EMAIL PROTECTED] (Alvaro Herrera) writes:
David Rowley escribió:
Or is sponsoring a feature paying money to people that already plan to
implement something?
Nobody on their mind would plan to implement the features being proposed
here ... I didn't look very far but it seems mainly
[EMAIL PROTECTED] (Dave Page) writes:
On Fri, Nov 14, 2008 at 8:10 AM, Simon Riggs [EMAIL PROTECTED] wrote:
On Fri, 2008-11-14 at 02:21 +, Gregory Stark wrote:
On the other hand what does occur to me in retrospect is that I regret
that I didn't think about how I was disparaging the
and...@dunslane.net (Andrew Dunstan) writes:
Robert Haas wrote:
I am personally quite tired of reviewing patches for people who don't
in turn review mine (or someone's). It makes me feel like not
working on this project. If we can solve that problem without
implementing a policy of this
j...@commandprompt.com (Joshua D. Drake) writes:
On Mon, 2009-11-16 at 11:31 -0500, Chris Browne wrote:
Ah, but the thing is, what was proposed wasn't totally evilly
draconian.
There's a difference between:
You haven't reviewed any patches - we'll ignore you forever!
and
Since
g...@turnstep.com (Greg Sabino Mullane) writes:
BTW, did we discuss the issue of 2PC transactions versus notify?
The current behavior of 2PC with notify is pretty cheesy and will
become more so if we make this change --- you aren't really
guaranteed that the notify will happen, even though the
pete...@gmx.net (Peter Eisentraut) writes:
On ons, 2009-11-25 at 16:27 +0100, Magnus Hagander wrote:
Attached is a patch which adds a chapter to git in our documentation,
around where we have several chapters about cvs today. It also removes
a few very out of date comments about cvs
I think
dp...@pgadmin.org (Dave Page) writes:
Congratulations!
+1
Congratulations, indeed, to this worthy set of developers!
--
output = reverse(moc.liamg @ enworbbc)
http://linuxfinances.info/info/multiplexor.html
Power tends to corrupt and absolute power corrupts absolutely.
-- First Baron
t...@sss.pgh.pa.us (Tom Lane) writes:
Robert Haas robertmh...@gmail.com writes:
On Mon, Dec 7, 2009 at 9:48 AM, Bruce Momjian br...@momjian.us wrote:
I wonder if we should rephrase this as, How hard will this feature be
to add, and how hard will it be to remove in a few years if we decide we
This is a C front end for the LLVM compiler... I noticed that it
entered Debian/Unstable today:
http://packages.debian.org/sid/main/clang
I thought it would be interesting to see if PostgreSQL compiles with
this, as an alternative compiler that should presumably become more and
more available
age...@themactionfaction.com (A.M.) writes:
[Much of interest elided... Cool to see that clang clearly *can*
compile PostgreSQL...]
You are probably running configure with gcc, no?
I was *attempting* to run configure using clang:
CC=/usr/bin/clang ./configure
j...@commandprompt.com (Joshua D. Drake) writes:
On the other hand ANALYZE also:
1. Uses lots of memory
2. Lots of processor
3. Can take a long time
We normally don't notice because most sets won't incur a penalty. We got a
customer who
has a single table that is over 1TB in size... We
robertmh...@gmail.com (Robert Haas) writes:
On Fri, Jan 8, 2010 at 10:12 AM, Dave Page dp...@pgadmin.org wrote:
I have long spoken against making Windows a second class citizen. But I
don't think David is going to do that (and I'll hound him if he does). But
that doesn't mean it has to be
bada...@gmail.com (Alex Hunsaker) writes:
On Fri, Jan 8, 2010 at 02:03, Magnus Hagander mag...@hagander.net wrote:
You can always create your own branch with just the .gitignore files
and merge that into whatever you're working on :)
The only thing annoying about that is if you generate diffs
kevina...@hotmail.com (Kevin Ar18) writes:
Of course all of this is from the perspective of Python users. Of
course, you have your own features that you want from your end (from
PostgreSQL's perspective). Perhaps this info would help you to know
which avenue to pursue.
No, those seem like
rocr...@gmx.de (Robert Doerfler) writes:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding support
for a platform that has such marginal usage.
Because someone feels
scra...@hub.org (Marc G. Fournier) writes:
On Tue, 16 Feb 2010, Bruce Momjian wrote:
I hate to pour cold water on this, but why is it worth adding
support for a platform that has such marginal usage.
Because someone feels like dedicating their resources to it ... ?
But adding it in would
t...@sss.pgh.pa.us (Tom Lane) writes:
Merlin Moncure mmonc...@gmail.com writes:
On Tue, Feb 16, 2010 at 10:38 AM, Tom Lane t...@sss.pgh.pa.us wrote:
2. Add an extra lock to serialize writers to the queue, so that messages
are guaranteed to be added to the queue in commit order. As long as
scrawf...@pinpointresearch.com (Steve Crawford) writes:
Marc G. Fournier wrote:
Is there a higher then normal amount of earthquakes happening
recently? haiti, japan just had one for 6.9, there was apparently
one in illinos a few weeks back, one on the Russia/China/N.Korean
border and now
francois.pe...@free.fr (François Pérou) writes:
* I am very surprised by the SQL level of Php developers. The example
Drupal developers trying to rewrite SQL queries dynamically adding
DISTINCT clause is just an example. So don't expect them to understand
the difference between MySQL and
si...@2ndquadrant.com (Simon Riggs) writes:
On Tue, 2010-03-16 at 15:29 +, Greg Stark wrote:
big batch delete
Is one of the reasons for partitioning, allowing the use of truncate.
Sure, but it would be even nicer if DELETE could be thus made cheaper
without needing to interfere with the
joeyadams3.14...@gmail.com (Joseph Adams) writes:
I introduced myself in the thread Proposal: access control jails (and
introduction as aspiring GSoC student), and we discussed jails and
session-local variables. But, as Robert Haas suggested, implementing
variable support in the backend would
robertmh...@gmail.com (Robert Haas) writes:
On Tue, Mar 30, 2010 at 8:58 PM, Josh Berkus j...@agliodbs.com wrote:
I'd think that you could get quite a long ways on this, at least doing
something like dbslayer without *necessarily* needing to do terribly
much work inside the DB engine.
robertmh...@gmail.com (Robert Haas) writes:
On Wed, Apr 28, 2010 at 1:40 PM, Dimitri Fontaine
dfonta...@hi-media.com wrote:
Robert Haas robertmh...@gmail.com writes:
Well, how would you define CREATE OR REPLACE TABLE? I think that
doesn't make much sense, which is why I think CREATE IF NOT
[EMAIL PROTECTED] (Tom Lane) writes:
Simon Riggs [EMAIL PROTECTED] writes:
Well it certainly seems worth separating them. It does seem possible
that recursive toasting effected some of the earlier results we looked
at.
Would you like me to do this, or will you?
I'm willing to do the code
[EMAIL PROTECTED] (Tom Lane) writes:
Chris Browne [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] (Tom Lane) writes:
... tuning the TOAST parameters seems like
something we understand well enough already, we just need to put some
cycles into testing different alternatives. I would have
[EMAIL PROTECTED] (Tom Lane) writes:
Bruce Momjian [EMAIL PROTECTED] writes:
The big question is whether this is for 8.3 or 8.4.
What I would definitely like to see for 8.3 is some performance testing
done to determine whether we ought to change the current defaults.
(Both
ler@lerctr.org (Larry Rosenman) writes:
I might use that as the base then, since the hardware finishes getting here
tomorrow.
My question still stands on what OS's we need coverage for.
I've got Debian testing/unstable covered. I'm not sure we have
Novell/SuSE covered...
--
output =
[EMAIL PROTECTED] (Florian G. Pflug) writes:
Martin Langhoff wrote:
Hi Florian,
I am right now running an rsync of the Pg CVS repo to my work
machine to
get a git import underway. I'm rather keen on seeing your cool PITR Pg
project go well and I have some git+cvs fu I can apply here (being
[EMAIL PROTECTED] (Aidan Van Dyk) writes:
I've diffed a CVS checkout and a git checkout, and the are *almost*
identical. Almost, because it seems like my git repository currently has 3
files that a cvs checkout doesn't:
backend/parser/gram.c |12088 +++
[EMAIL PROTECTED] (Bruce Momjian) writes:
I have seen no one do peroformance testing of this, so it seems it
will have to wait for 8.4.
I didn't have time...
I'll see if I can find a decent place to document how to tweak the
threshold, as that seems like it could be worth doing in cases where
[EMAIL PROTECTED] (Tom Lane) writes:
Chris Browne [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] (Bruce Momjian) writes:
I have seen no one do peroformance testing of this, so it seems it
will have to wait for 8.4.
I didn't have time...
(e.g. - we've got a case where dropping the threshold
[EMAIL PROTECTED] (Marc Munro) writes:
On Mon, 2007-30-04 at 08:56 -0300, Heikki Linnakangaspgsql wrote:
Date: Mon, 30 Apr 2007 09:18:36 +0100
From: Heikki Linnakangas [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED]
Cc: Dave Page [EMAIL PROTECTED], Simon Riggs
[EMAIL PROTECTED],
Bruce
[EMAIL PROTECTED] (Andrew Dunstan) writes:
Tom Lane wrote:
So in a roundabout way we come back
to the idea that we need a bug tracker (NOT a patch tracker), plus
people putting in the effort to make sure it stays a valid source
of up-to-date info. Without the latter it won't really be
[EMAIL PROTECTED] (Josh Berkus) writes:
Bruce,
Realistically I just don't see getting everything in the ToDo patch
list in; my vote is that we start deferring stuff for 8.4 if it
doesn't have a reviewer, except for items which were submitted early
in the cycle (and to whom it would be
[EMAIL PROTECTED] (Aidan Van Dyk) writes:
* Tatsuo Ishii [EMAIL PROTECTED] [070516 07:23]:
Maybe. However I think subject-sequence has some advantages over
Message-Id:
- Easy to identify. Message-Id may not appear on some MUA with default
setting
- More handy than lengthy message Id
[EMAIL PROTECTED] (Bruce Momjian) writes:
The results are here:
http://momjian.us/expire/TOAST/
I'll take a look and see if there's anything further it makes sense
for me to try testing. Thanks for following up so quickly; what with
the cold I have had, I haven't yet gotten back to the
I'm seeing some applications where it appears that there would be
value in introducing asynchronous messaging, ala message queueing.
http://en.wikipedia.org/wiki/Message_queue
The granddaddy of message queuing systems is IBM's MQ-Series, and I
don't see particular value in replicating its
[EMAIL PROTECTED] (Steve Atkins) writes:
Is there any existing work out there on this? Or should I maybe be
looking at prototyping something?
The skype tools have some sort of decent-looking publish/subscribe
thing, PgQ, then they layer their replication on top of. It's multi
consumer and
[EMAIL PROTECTED] (Marko Kreen) writes:
To Chris: you should like PgQ, its just stored procs in database,
plus it's basically just generalized Slony-I, with some optimizations,
so should be familiar territory ;)
Looks interesting...
Random ideas
- insert_event in C (way to get
[EMAIL PROTECTED] writes:
On Wed, Jul 11, 2007 at 12:38:09AM -0400, Tom Lane wrote:
[EMAIL PROTECTED] writes:
[...]
It might make sense then to clear the pg_twophase directory on DB
startup.
blink I fear you have 100% misunderstood the point. The *only*
reason for that feature is to
[EMAIL PROTECTED] (Stefan Kaltenbrunner) writes:
Tom Lane wrote:
[...]
animal: clownfish warnings: 12
dynloader.c, line 4: warning: empty translation unit
postgres.c, line 3758: warning: loop not entered at top
The first of these is not a bug, the second seems to be some weird
[EMAIL PROTECTED] (Peter Eisentraut) writes:
Am Mittwoch, 18. Juli 2007 13:21 schrieb Magnus Hagander:
The main reasons would be to have less code to maintain,
I don't think the krb5 support has needed all that much maintenance in the
last few years.
and to make life
easier for
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective implementations,
seeing some similarities and differences. He pointed out one aspect
of index handling
[EMAIL PROTECTED] (Dawid Kuroczko) writes:
On 8/14/07, Chris Browne [EMAIL PROTECTED] wrote:
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective
[EMAIL PROTECTED] (Gregory Stark) writes:
Heikki Linnakangas [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
That general approach of storing a common part leading part just once is
called prefix compression. Yeah, it helps a lot on long text
[EMAIL PROTECTED] (Joshua D. Drake) writes:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heikki Linnakangas wrote:
Joshua D. Drake wrote:
I guess my point is, if the patch looks good and does not appear
to hurt anything, why not apply it? At
[EMAIL PROTECTED] (Tom Lane) writes:
The main thing that is lacking at the moment is documentation. The
stuff Bruce has been working on will be good introductory material,
but we've got basically zip in reference material. I'll do some work
on that over the next couple of days, but there's
[EMAIL PROTECTED] (Jan Wieck) writes:
On 9/7/2007 11:01 AM, Markus Schiltknecht wrote:
None the less, Postgres-R is eager (or pessimistic?) in the sense
that it replicates *before* committing, so as to avoid
divergence. In [1] I've tried to make that distinction clear, and
I'm currently
[EMAIL PROTECTED] (Teodor Sigaev) writes:
* Draft release notes --- can't really ship a beta without these,
else beta testers won't know what to test. Traditionally this has
taken a fair amount of time, but I wonder whether we couldn't use
http://developer.postgresql.org/index.php/WhatsNew83
[EMAIL PROTECTED] (Bruce Momjian) writes:
I think we need another week to get things ready for beta. I will have
the release notes done mid-week and hopefully we can close out all open
items by the end of the week.
It's worth noting that Greg Smith has collected release note
information into
pete...@gmx.net (Peter Eisentraut) writes:
On Fri, 2009-09-25 at 16:59 -0400, Tom Lane wrote:
shakahsha...@gmail.com shakahsha...@gmail.com writes:
From pg_dump/pg_restore section (9.2 of the Todo page on the
PostgreSQL Wiki), is the following item
Add comments to output indicating
sfr...@snowman.net (Stephen Frost) writes:
* David Fetter (da...@fetter.org) wrote:
On Sun, Oct 04, 2009 at 04:07:40PM -0400, Robert Haas wrote:
The radical proposal was the RULE system. It's been tested now,
and it's pretty much failed.
You still haven't explained what actual
dp...@pgadmin.org (Dave Page) writes:
As Tom says though, the effect this has on users is zero. The licence
is still the same as its always been, regardless of what we say it is
based on or looks like.
There may be a fairly miniscule one...
There do exist GPL zealots that bash, as not free
arta...@comcast.net (Scott Bailey) writes:
Disk format - A period can be represented as [closed-closed],
(open-open), [closed-open) or (open-closed] intervals. Right now we
convert these to the most common form, closed-open and store as two
timestamptz's.
I mentioned this at the 2009 PGCon,
[EMAIL PROTECTED] (Bruce Momjian) writes:
Added to TODO:
* Allow one transaction to see tuples using the snapshot of another
transaction
This would assist multiple backends in working together.
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php
FYI, code for this is
[EMAIL PROTECTED] (Heikki Linnakangas) writes:
Josh Berkus wrote:
Maybe we should make the next commit-fest June 1 to give people some
time off? And some time to improve the tools?
I would rather do the commit fests often, to keep the patch queue and
the commit fests short.
But if it means
[EMAIL PROTECTED] (Joshua D. Drake) writes:
The base requirements for this process must be so simple, so easy, that
even if the person has never seen a C patch in his/her life they
understand what is trying to be achieved.
Are you sure about that?
I think that our concern is about the sort
[EMAIL PROTECTED] (Tom Lane) writes:
In short, I think it's time to declare our first commit fest done.
Congratulations!
As a pure observer in the matter, it has clearly been a somewhat
painful process, which must be tempered by the consideration that what
was being reviewed was pretty much a
[EMAIL PROTECTED] (Tom Lane) writes:
Magnus Hagander [EMAIL PROTECTED] writes:
I think pg_indent has to be made a lot more portable and easy to use
before that can happen :-) I've run it once or twice on linux machines,
and it comes out with huge changes compared to what Bruce gets on his
[EMAIL PROTECTED] (Bruce Momjian) writes:
Magnus Hagander wrote:
And I think adopting surrounding naming, commeting, coding conventions
should come naturally as it can aide in copy-pasting too :)
I think pg_indent has to be made a lot more portable and easy to use
before that can happen
[EMAIL PROTECTED] (Bruce Momjian) writes:
Chris Browne wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
Magnus Hagander wrote:
And I think adopting surrounding naming, commeting, coding conventions
should come naturally as it can aide in copy-pasting too :)
I think pg_indent has
[EMAIL PROTECTED] (Bruce Momjian) writes:
Chris Browne wrote:
Would it be a terrible idea to...
- Draw the indent code from NetBSD into src/tools/pgindent
- Build it _in place_ inside the code tree (e.g. - don't assume
it will get installed in /usr/local/bin)
- Thus have
[EMAIL PROTECTED] (Simon Riggs) writes:
Should there be a new rule option? ie. ON MERGE rules ?
Maybe, but not as part of this project.
That seems to warrant a bit of elaboration...
If we're running a MERGE, and it performs an INSERT or UPDATE of a
particular tuple in(to) a particular
[EMAIL PROTECTED] (Tom Lane) writes:
Chris Browne [EMAIL PROTECTED] writes:
Would it be a terrible idea to...
- Draw the indent code from NetBSD into src/tools/pgindent
I am not real eager to become maintainers of our own indent fork, which
is what you propose. (Just for starters, what
[EMAIL PROTECTED] (Stephen Frost) writes:
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
Around http://archives.postgresql.org/pgsql-patches/2008-01/msg00089.php
it
was proposed to truncate the psql welcome screen. What do you think about
that?
I'd recommend an option in .psqlrc to
[EMAIL PROTECTED] (Bruce Momjian) writes:
I am impressed at the state of the May wiki patch queue:
http://wiki.postgresql.org/wiki/CommitFest:May
It is even tracking the psql wrap patch I am working on now.
Aside: I have made a few little changes that oughtn't be too
controversial:
1.
There's a new #include file that it turns out we need for Slony-I to
reference, namely include/server/utils/snapmgr.h
I tried adding an autoconf rule to Slony-I to check for its existence
(goal then is to do a suitable #define so that we can #ifdef the
#include, so that we #include this only with
[EMAIL PROTECTED] (Alvaro Herrera) writes:
Chris Browne wrote:
If I use:
AC_CHECK_HEADER(utils/snapmgr.h, HAVE_SNAPMGR=1)
this turns out to fail. Apparently autoconf wants to compile the
#include file to validate that it's an OK #include file.
GCC barfs on it, thus:
[EMAIL
[EMAIL PROTECTED] (Decibel!) writes:
On Apr 22, 2008, at 1:17 PM, Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
As I've said elsewhere, we could have it lock each row, its just more
overhead if we do and not necessary at all for bulk data merging.
I'll presume we want locking
[EMAIL PROTECTED] (Andrew Dunstan) writes:
Raphaël Jacquot wrote:
would seem like a good idea, no ?
http://www.murrayc.com/blog/permalink/2008/04/25/postgresql-has-no-bugzilla/
Before you come trolling on this (or any other) subject, please read
the voluminous debates that have taken place
[EMAIL PROTECTED] (Alvaro Herrera) writes:
Darren Reed wrote:
Because interacting with the database is always through an action
that you do and if you're being half way intelligent about it, you
are always checking that each action succeeded before going on to
the next.
Hmm, it won't be
[EMAIL PROTECTED] (Florian Weimer) writes:
* Thomas Mueller:
What do you think about it? Do you think it makes sense to implement
this security feature in PostgreSQL as well?
Can't this be implemented in the client library, or a wrapper around it?
A simple approximation would be to raise an
[EMAIL PROTECTED] (Tom Lane) writes:
As I said originally, we have no expectation that the proposed features
will displace the existing replication projects for high end
replication problems ... and I'd characterize all of Robert's concerns
as high end problems. We are happy to let those be
[EMAIL PROTECTED] (Andreas 'ads' Scherbaum) writes:
On Thu, 29 May 2008 23:02:56 -0400 Andrew Dunstan wrote:
Well, yes, but you do know about archive_timeout, right? No need to wait
2 hours.
Then you ship 16 MB binary stuff every 30 second or every minute but
you only have some kbyte real
[EMAIL PROTECTED] (Greg Smith) writes:
On Fri, 6 Jun 2008, Heikki Linnakangas wrote:
Or perhaps we should explicitly mark the settings the tool has
generated, and comment out:
#shared_buffers = 32MB # commented out by wizard on 2008-06-05
shared_buffers = 1024MB # automatically set by
[EMAIL PROTECTED] (Simon Riggs) writes:
On Wed, 2008-06-25 at 23:34 -0400, Robert Haas wrote:
I can predict that Tom will say that the planning time it would take
to avoid this problem isn't justified by the number of queries that it
would improve.
That's possible, but it's unfortunate
[EMAIL PROTECTED] (Alvaro Herrera) writes:
Pavel Stehule escribió:
p.s. can we create some general F.A.Q XML format and store FAQ there?
WIP Proposal:
faq name = . language =
entry number=1.1.1
query/query
ansver
...
we need some tags from html: pbraibullitable
[EMAIL PROTECTED] (Josh Berkus) writes:
Simon,
We can issue a provisional date. We could also say at least 6 months
after release date of 8.3. I'm sure there's other options too.
I'm going to suggest 4 months after 8.3. 8.3 was supposed to be a *short*
release so that we could move our
[EMAIL PROTECTED] (Tom Lane) writes:
Simon Riggs [EMAIL PROTECTED] writes:
I'd suggest we have multiple checkpoints during the cycle. Checkpoint is
a patch queue blitz where we stop developing and reduce the queue to
nothing. Perhaps a two-week period where everybody helps reduce the
queue,
[EMAIL PROTECTED] (Tom Lane) writes:
Andrew Dunstan [EMAIL PROTECTED] writes:
Perhaps both these considerations dictate providing another command or a
special flavor of \l instead of just modifying it?
I've seen no argument made why \l should print this info at all.
Its interesting
[EMAIL PROTECTED] (Peter Eisentraut) writes:
Am Montag, 26. November 2007 schrieb Tom Lane:
Pavel Stehule [EMAIL PROTECTED] writes:
I propose new kind of FOR statement .. iteration over cursor,
This seems useless and probably syntactically ambiguous.
I think that is isomorphic to what he
[EMAIL PROTECTED] (Simon Riggs) writes:
I think we have an opportunity to bypass the legacy-of-thought that
Oracle has left us and implement something more usable.
This seems like a *very* good thing to me, from a couple of
perspectives.
1. I think you're right on in terms of the issue of the
[EMAIL PROTECTED] (Markus Schiltknecht) writes:
Simon Riggs wrote:
With that in mind, can I clarify what you're thinking, please?
Sure, I can try to clarify:
2) the things you've been discussing are essential requirements of
partitioning and we could never consider it complete until they
Ron Mayer [EMAIL PROTECTED] writes:
Chris Browne wrote:
_On The Other Hand_, there will be attributes that are *NOT* set in a
more-or-less chronological order, and Segment Exclusion will be pretty
useless for these attributes.
Really?I was hoping that it'd be useful for any data
[EMAIL PROTECTED] (Simon Riggs) writes:
On Fri, 2008-01-11 at 20:39 +, Simon Riggs wrote:
On Fri, 2008-01-11 at 15:05 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
If we had a function
replace_serializable_snapshot(master_xid, txid_snapshot)
this would allow us to
[EMAIL PROTECTED] (Amit jain) writes:
What are the Data Recovery feature available in postgreSQL apart
from pg_restore and PITR. If my Database has corrupted its not
starting which feature i can use for Data Recovery ? Any help
willbe highly appreciated.
The primary mechanism for database
[EMAIL PROTECTED] (Pedro Belmino) writes:
I am creating an agent that runs alongside the postgres written in
c++, I have a question: How send sql queries directly for the
database without going need to make any connection? What I
call function, which I use file?
You don't do that; your
d...@csail.mit.edu (Dan Ports) writes:
I'm not clear on why the total rowcount is useful, but perhaps I'm
missing something obvious.
It would make it easy to conclude:
This next transaction did 8328194 updates. Maybe we should do
some kind of checkpoint (e.g. - commit transaction or
heikki.linnakan...@enterprisedb.com (Heikki Linnakangas) writes:
On 24/05/10 19:51, Kevin Grittner wrote:
The only thing I'm confused about is what benefit anyone expects to
get from looking at data between commits in some way other than our
current snapshot mechanism. Can someone explain a
br...@momjian.us (Bruce Momjian) writes:
Jan Wieck wrote:
The point is not that we don't have that information now. The point is
having a hint BEFORE wading through possibly gigabytes of WAL or log data.
If getting that information requires to read all the log data twice or
the need to
gsst...@mit.edu (Greg Stark) writes:
On Wed, Jun 2, 2010 at 6:45 PM, Chris Browne cbbro...@acm.org wrote:
It would make it easy to conclude:
This next transaction did 8328194 updates. Maybe we should do
some kind of checkpoint (e.g. - commit transaction or such) before
working
mag...@hagander.net (Magnus Hagander) writes:
I concur with the thought that the most useful solution might be a way
to tell pg_restore to remove or disable check constraints.
Uh, say what? Are you saying pg_restore should actually remove
something from the database schema? And thus no longer
I'm trying to start preparing buildfarm nodes for the upcoming Git
migration, and have run into a few issues. I speculate that -hackers
is one of the better places for this to get discussed; if it should be
elsewhere, I'm sure Andrew Dunstan won't be shy to redirect this :-).
What I was hoping
si...@2ndquadrant.com (Simon Riggs) writes:
Just for the record, I've never ever met anyone that said Oh, this
\d syntax makes so much sense. I'm a real convert to Postgres now
you've shown me this. The reaction is always the opposite one;
always negative. Which detracts from our efforts
robertmh...@gmail.com (Robert Haas) writes:
On Thu, Aug 5, 2010 at 11:43 AM, Simon Riggs si...@2ndquadrant.com wrote:
Looks like MERGE is progressing well.
At 2010 Dev Mtg, we put me down to work on making merge work
concurrently. That was garbled slightly and had me down as working on
mmonc...@gmail.com (Merlin Moncure) writes:
On Wed, Aug 4, 2010 at 9:31 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Aug 4, 2010 at 6:43 PM, Merlin Moncure mmonc...@gmail.com wrote:
*) also, isn't it possible to change text cast influencing GUCs 'n'
times per statement considering any
101 - 200 of 252 matches
Mail list logo
