worthless because the test ran for a
trivial amount of time? Seems like it happens a lot to me. This patch
was already on my todo list for 8.4 and I'm glad I don't have to write it
myself now.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-
uot;Most people have no idea how to set [GUCs]" which I know some
people wanted to see a more formal document for before mucking with any of
the code. I'll have something to announce there shortly.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via p
articular machine, so that all those numbers
actually can be tied to some real-world time measure. If you did that,
you'd actually have a shot at accomplishing the real goal here, making
statement_cost_limit cut off statements expected to take longer than
statement_timeout before they even ge
obe in the middle there to make that straightforward.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
both.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
available.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Windows as well, at least enough to
cover this particular issue.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
cleanup/wizard plan that's being worked on. The pg_settings view
really should show the value both as the user input it and as it's stored
internally for cases like these, which lowers the confusion here a bit
even without going so far as converting everything to bytes.
--
* Greg Smi
e amount of layering
in this area makes it difficult to understand just what's going on
sometimes (especially when new to it). A lot of that abstraction felt a
bit pass-through to me, and anything that would collapse that a bit would
be helpful for streamlining the code instrumenting going
ook useful and consistant, then move toward
cleaning up broader compatibility issues like the segfault concerns Zoltan
mentioned.
Going to take a while to work through all that, but performance patches
with platform-specific benefit are always painful like this.
--
* Greg Smith [EMAIL PROTECTED]
restored a previous version after a crash that
didn't save an updated copy.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
itself, I like
http://doxygen.postgresql.org/
4) Notes on how to deal with version control issues, patch submission, and
to find out what development is going on currently are all at
http://wiki.postgresql.org/wiki/Development_information
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com
tting new
features implemented.
Maybe all that's needed is to extend the "provides" section there with a
tag for those who are willing to take that sort of work on.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing
make it easier for potential sponsors to navigate.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
about their server, or
sometimes that they're even using PostgreSQL inside the firewall. If it's
not a tool that you can run on the same server you're running PostgreSQL
on, I'd consider that another diversion that's not worth pursuing.
--
* Greg Smith [EMAIL PROTECTED]
lving the newbie problem. I want a tool to help out
tuning medium to large installs, and generating a simple config file is
absolutely something that should come out of that as a bonus. Anything
that just targets the simple installs, though, I'm not very motivated to
chase after.
--
* Greg Sm
.
I don't think these people need guidance on how to manage the project,
they need some sort of way to feel comfortable saying "will pledge $Y for
feature $X" in a way that makes sense on both sides.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
implementation.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
range, and recommended setting are all valuable things people
would like to see when deciding what the change a setting to. And there's
no reason accumulating all that info should be the responsibility of a
tool writer when it's easy to expose and keep up to date inside the
database itsel
On Fri, 6 Jun 2008, Gregory Stark wrote:
"Greg Smith" <[EMAIL PROTECTED]> writes:
1) Is it worthwhile to expand the information stored in the GUC structure to
make it better capable of supporting machine generation and to provide more
information for tool authors via pg_sett
osh) didn't
just make them all up out of nowhere you know. I wrote a message here
already about what the seemingly inevitable path the budding "wizard tool
hacker" follows and why that leads into some of the changes suggested.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.co
topic now) to hash out suggestions in this area, I'm trying to keep this
somewhat thread focused now.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://ww
require messing around with kernel settings
that no PostgreSQL tool can really help with.
Yes. So? All you can do is point this out to users.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
mock-up showing what each of the outputs from the
pg_generate_conf tool might look like to get feedback on that; it will
make what is planned here a bit easier to understand as well.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (
leting all of the continuing attemps to
divert the discussion over to parameter tuning details or expanding the
scope here.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
he settings I tinker with do,
but even I'd like it to be easier to find the right spot in the manual;
for newbies it's vital. You are correct that (2) isn't strictly necessary
here, but it's valuable and will be easier to wrap into this than to bolt
on later.
(3) (4) (5)
h a proper
API.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
rformance
tuning document a bit more in people's faces might help lower some of the
criticism the project takes over providing low defaults for so many
things.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-ha
In the shared_buffers case, it may be possible to just recommend a
value without caring one bit what the current one is. But for work_mem,
you really need to actually understand the value if you want any real
intelligence that combines that information with the maximum connections,
so that you can
e moving along at their own pace.
There's already more tuning knowledge available than tools to help apply
that knowledge to other people's systems, which is why I think a diversion
to focus just on that part is so necessary.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Bal
urther outbursts about non-productive comments
here, and each time I am tempted instead work on prototyping the necessary
code I think this really needs instead.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
hat should show at the very
beginning.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
en running for a while (and possibly moved to another
machine). By that point nobody wants to mess with their configuration
file unless it's one simple change at a time.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgs
hat on an XML file in
any shell language in that class, then we might have something to talk
about.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
are dealt with first, and that's where this is at right now.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ybody who could pull it
off who isn't already overtasked with more important improvements for the
8.4 timeframe.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to you
On Mon, 2 Jun 2008, Tom Lane wrote:
Greg Smith <[EMAIL PROTECTED]> writes:
Joshua has been banging a drum for a while now that all this data needs to
get pushing into the database itself.
This is, very simply, not going to happen.
Right, there are also technical challenges in the
l planned out if you look
at his presentations, but without the larger overhaul it's just not
possible to make the implementation elegant.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ttp://wiki.postgresql.org/wiki/GUCS_Overhaul I think reading
that version makes it a bit clearer what the proposed overhaul is aiming
for.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
evable to clone a working facsimile of
even a complicated postgresql.conf file set remotely just by reading
pg_settings.
While a bit outside of the part you're specifically aiming to improve
here, if you could slip these two additions in I think it would be a boon
to future writers of multi
because all the
unused bytes are 0. File comes out the same size at the other side, but
you didn't ship a full 16MB if there was only a few KB used.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
ant
March commitfest queue but should probably wander into contrib as part of
8.4.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
;s the
case, it would be nice to explicitly spell out what that was to deflect
criticism of the planned prioritization.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
h
what the data is in some
environments, and in some of those downtime is really, really expensive.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.post
d to
http://www.westnet.com/~gsmith/content/postgresql/ and read "Inside the
PostgreSQL Buffer Cache".
The work memory allocated for sorting is separate from that, and it
doesn't cache anything. It just provides working room for a query that's
being executed right
our input files into smaller chunks and loads them,
kicking back the ones that don't load, or breaking them into even smaller
chunks until you've found the problem line or lines.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list
ay in sync as the underlying log file changes
(it might rotate every day for example). Unfortunately it's not as simple
as just using tail.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
useful purchase for one of the PG
non-profits to make one day though.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ng_with_CVS#Initial_setup
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
milated into core as well so they don't have to
maintain their patch past 8.3; hopefully Theo or Robert will chime in on
that.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
echnically, but I don't think the introduce any real
functional creep. It would be difficult to even strip a system down to
the point where these packages weren't available.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing
defense
mechanisms these environments look for redundant layers of security. In
reality users of this would aim for a completely locked down base
PostgreSQL *and* a completely locked down SELinux implementation
integrated into that, reinforcing one another, rather than just relying on
one le
tgreSQL ones, but it should be easier to change policy
violations that impact the server to something other than just ERROR.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to you
llion errors reported
just because there's data that person can't see available.
At a minimum, this needs some finer log control, and maybe a rethinking
altogether of how to handle error cases.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via p
take it seriously, and the whole thing just leaves me feeling sorry for
them instead.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
control might work well. Maybe have an "adjust estimates for cache
contents" knob that you can toggle on a per-session or per-table basis?
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the additional toolchain
needed for reST processing just to make the FAQ a little easier to edit.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgres
be a useful hack when a page gets removed or to
handle common shortcuts/errors. In general, if you're relying on them
heavily for external navigation structure, you're probably not using the
right tool for that sort of job.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Ba
On Sat, 19 Apr 2008, Joshua D. Drake wrote:
Greg Smith wrote:
One small change I'd suggest on the main site:
http://www.postgresql.org/developer/coding links to
http://wiki.postgresql.org/wiki/Developer_and_Contributor_Resources which
is now a redirect to the above page.
This re
ut the advocacy
contributors to their own section which made the longer title unneeded.
It would be nice one day to change that to use the shorter
Development_information URL instead. It would also be worth considering a
direct link to that URL in the manual, I believe it will remain stable
isn't good enough here? http://doxygen.postgresql.org/globals_type.html
Scraping that HTML seems like it would be pretty straightforward.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
he academic users of PostgreSQL were hoping to
add features in this area in order to allow better using planner internals
for educational purposes. It would be nice if that were available for
such purposes without having to recompile.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Ba
yet. That whole area of the Wiki is still
moving around a bit, and I expect some more usefully targetted pages will
emerge ("How to submit a patch" comes to mind). Having a stable
CommitFest URL is handy, but I don't think it's where the FAQ should be
sending people.
--
n whenever a
specific wiki page is modified right now, that's a standard MediaWiki
feature. If you wanted you could even sign up a mailing list as the
entity being notified. That's not exactly what you had in mind I think,
but it's close enough to be useful for now.
--
* Gr
do items and such rather than letting the idea just get
lost in the archives.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ict...err, volunteers to pull him out of
the later steps though for a net reduction in his time. Simply getting
things organized better from the start should help with getting more
people helping out with review; the common complaint seemed to be "I can't
figure out what to help w
(but not installed in the database, as you point out) unless
someone goes out of their way to circumvent that.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Other people have been
running such tools for Bruce but he doesn't have one he can become
comfortable with running himself yet.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chang
5 from
the above. But that's a one-way operation that doesn't really help with
the commenting situation, and it's inevitably going to lag behind the
mailbox-centered queue unless it's made fully automatic. I can't think of
anything better that doesn't require building so
o pull that off.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ginal code at http://mmmysql.sourceforge.net/performance/ , there's
also some improved versions at
http://developer.mimer.com/features/feature_16.htm
I'm not sure if all of those changes are net positive for PostgreSQL
though, they weren't last time I played with this.
--
mment
about whether those are worth the trouble to integrate. The big missing
piece of community hardware that remains elusive would be a system with
=4 cores, >=8GB RAM, and >=8 disks with a usable write-caching controller
in it.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.
my main concern about this experiment. Some
of the discussion that followed your original request for tests was kind
of confusing as far as how to interpret the results as well; I think I
know what to look for but certainly wouldn't mind some more guidance
there, too.
--
* Greg Smith [E
ones. And it's kind
of a touchy subject to bring up as well, since it's hard to make
recommendations without looking unprofessional--which partly explains the
dead silence you've gotten as a response here so far.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsm
with "case 'r'" and the 3 new variable
definitions just above it that uses).
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
re fixing a bug that's more
troublesome than that risk.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
now people have asked about simulating this
behavior, and I don't recall a good sample solution being presented before
yours.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
t the person who
starts the database will be surprised if the person stopping it isn't
paying attention (or isn't a person).
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ves I got the impression it was some page mapping issue but details
are elusive.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/
l project than a database one. I also have my doubts
about whether you could get this done within the GSoC timeframe; better to
pick a less ambitious goal than rewriting the whole storage manager
interface I would think.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimo
make
your own copy of the repository instead.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
code as an attachment for a proposal if you
can direct people to the web for them. That's why I suggested sending
"the minimum of files necessary", which in this case was zero.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers ma
practically on a wiki already!
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a similar independant
review will need to happen for every component you interact with here, on
top of a technical review. Luckily this is something a lot of people
would like and that should all get taken care of.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
uld
search based on them. A brief glance at the MHonArc documentation
suggests that could be run to re-covert any existing messages that are
still available in order to add to those even.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing
out what the reply was referring to.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.3 progress will make sense. Right now many of these
threads are not turning into patches to review, and the easiest way to
figure out which are which is to read through the discussion
thread--something a wiki wouldn't make any easier than the view Bruce is
already providing.
--
* Greg Smith
work done on postgresqldocs.org into
the new infrastructure in a couple of days, after things settle down a
bit.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
pages get moved over with the same names (which doesn't seem
like it would be a problem), just changing developer.postgresql.org to
point to wiki.postgresql would seem to be sufficient to keep any existing
links working.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, M
On Tue, 11 Mar 2008, Greg Smith wrote:
On Tue, 11 Mar 2008, Magnus Hagander wrote:
How about we move it to the wiki. AFAIK we can still lock it down to who
can edit it if we want to
You should confirm you can get the editing granularity you want before making
too many plans here if this is
developer's wiki.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, 7 Mar 2008, Heikki Linnakangas wrote:
If I want people to review my patch, I'm ready to sing and dance if
that's what it takes.
Great timing, there's even a suitable song available for you today:
http://use.perl.org/~grantm/journal/35855
--
* Greg Smith [EMAIL
make today is
that I'd prefer not to see commit_delay excised until there's a superior
replacement for it that's suitable even for synchronous write situations.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-ha
t thing, but I hope
it's obvious that there's some possibility to improve this area for
applications that can't use async commit. If you're going to dump the
feature, I'd suggest at least waiting until later in the 8.4 cycle to see
if something better comes along first.
nst that single file.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
mps, while a pg_dump focused
effort helps nothing but that specific workflow. I wonder if doing too
much work on the pg_dump path is the best use of someone's time when the
more general case will need to be addressed one day anyway.
--
* Greg Smith [EMAIL PROTECTED] http://www.gr
tion between the bgwriter
and the backend doing COPY
It might be worthwhile to turn off the background writer for these runs,
both to see if it changes anything and to simplify the output.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---
te as people mention new ones.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
. That sort of thing (renamed or improperly continued thread on the
same topic) is another spot where someone keeping track of things manually
can end up with a more consistant view of the discussion than the archives
provide.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.co
ds, but there is some value
to the way Bruce collects up the more interesting posts in the thread.
--
* Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
1301 - 1400 of 1570 matches
Mail list logo
