to generate the plan this way.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Josh Berkus [EMAIL PROTECTED] writes:
DW:
default_statistics_target = 400
Mixed:
default_statistics_target = 100
You, my friend, are certifiably insane.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support
that I
didn't think about how I was disparaging the importance of mental illness and
hope nobody took offense for that reason.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql
your back. But when
you're reading the data back in you don't have to worry about that.
I'm a bit surprised to hear our CRC implementation is a bytewise loop. I
thought it was much faster to process CRC checks word-wise.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
be hard to do it in any
kind of abstract away like you were describing.
How happy are you with the wal logging entries? Have you done any tests to see
how much extra wal traffic it is? Are you sure you always generate enough logs
soon enough?
--
Gregory Stark
EnterpriseDB http
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark wrote:
I think you could checksum the block including the hint bits then go back and
remove them from the checksum.
I'm not sure what you're proposing here. It sounds to me like you are
saying that we can read the page, make
expanding the page header. The user wouldn't have to know about
these, the tool would set it for him.
If we're worried about expanding tuple header overhead then we would need a
separate option. If we grow any data type representations then we could still
have a problem.
--
Gregory Stark
operation.
But doesn't this problem go away if you do it in a transaction? You
set xmax on the old tuple, write the new tuple, and add index entries
just as you would for a normal update.
But that doesn't actually solve the overflow problem on the old page...
--
Gregory Stark
Martijn van Oosterhout [EMAIL PROTECTED] writes:
On Wed, Nov 05, 2008 at 09:41:52PM +, Gregory Stark wrote:
Robert Haas [EMAIL PROTECTED] writes:
Problem is how to move tuple from page to another and keep indexes in
sync.
One solution is to perform some think like update operation
understanding was complete-ly
wrong and your comments seem accurate.
What I would appreciate is a README explaining how vacuum and vacuum full
work.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers
it is, then
you're still in the category he described.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
not be an online
process.
In any case it sounds like you're saying you want to allow multiple versions
of tuples on the same page -- which a) would be much harder and b) doesn't
solve the problem since the page still has to be converted sometime anyways.
--
Gregory Stark
EnterpriseDB
proposed a system
where that wasn't true.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
an optimization
over just doing the whole page right away.)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Joshua D. Drake [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Robert Haas [EMAIL PROTECTED] writes:
An old page which never goes away. New page formats are introduced for a
reason -- to support new features. An old page lying around indefinitely
means
some pages can't support those new
tuple in the cases where it
needs to examine the result, and no one else presently cares at all.
But the possibility of overflow might limit the usefulness of this
definition in other scenarios.
And what would that mean for a cursor which was read forward and backward?
--
Gregory Stark
? And if the patch is too huge, is it
better to split the patch than send an external link?
I suppose you could upload the patch to the wiki which just gives a warning
but lets you go ahead.
Isn't this like the third time we've run into this and said we were going to
raise/erase the limit?
--
Gregory
nonsensical page headers.
3. Don't read the page from disk, just allocate a buffer. (ReadOrZeroBuffer())
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
is set and that causes the crc to be set to the invalid sum
will we ever get another chance to set it?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
going to make CRCs mandatory? Or set aside
the 4 bytes even if you're not using them? Because if the size of the page
header varies depending on whether you're using CRCs that sounds like it would
be quite a pain.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
at I
believe.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
reworking of
these parameters and I don't want to go there...
posix-fadvise-v19.patch.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers
was including the
type oid in the toast chunks. I suppose attribute number might be just as good
-- it would let you save upgrading chunks for dropped columns at the expense
of having to look up the column info first.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
be looking at the chunk in which the
desired offset lies.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
steps.
Now your patch isn't affecting that one way or the other but does it rule it
out forever?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
a raid array it would be worthwhile to do the equivalent of a bitmap heap
scan by fetching blocks in order.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsql-hackers mailing
).
There might also have been a question of how to deal with the statistics.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2008-10-28 at 10:59 +, Gregory Stark wrote:
To do that he proposed we do:
1. scan heap doing two things: a) remove any marked tuples if they were
marked
by a previous vacuum which committed and b) prune and mark any tuples we
find
not likely to be
running modern OSes anyways?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2008-10-28 at 12:34 +, Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I've never liked it -- I
always hated that in Oracle and thought it was a terrible kludge.
But now... If you have a better way, great, but that doesn't make
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2008-10-28 at 17:40 -0400, Bruce Momjian wrote:
Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I'm happy with the idea of a readahead process. I thought we were
implementing a BackgroundReader process for other uses
side are and how many are
distinct values.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
we'll always have a terrible half-baked language.
Building a whole language with clean syntax and consistent semantics is a lot
of work.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list
. If
you visit an insecure web site you get your web page. But if you visit a
secure web site with a bogus certificate you get a big warning.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing
a *huge* error and refuses to connect.
Preventing casual snooping without preventing MitM is a rational choice
for system administrators.
I think the word you're looking for is naive :)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's
like:
5 IN (col1,col2,col3)
resulting in a bitmap or of three index scans of three different indexes on
col1, col2, and col3.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql
ams to stream results to the executor in bitmap form. That
would allow a scan of a bitmap index to return bitmap elements wholesale and
have the executor apply bitmap operations to them along with the elements
returned by a btree bitmap scan or other index ams.
--
Gregory Stark
EnterpriseDB
in WAL
recovery. Perhaps we should plan on being able to kill other processes holding
pins on the buffer just as we discussed killing transactions holding up
advancing the globalxmin.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres
for collation derivation.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the scheme you're describing would waste a huge amount of space
in every string on disk. For short strings it could triple the amount of space
(plus I think the explicit vs implicit collation would make it even worse).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
interesting than just getting better estimates :)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
* tupdesc has more columns than the tuple does. This is possible after
ALTER TABLE ADD COLUMN, for example. The correct interpretation in
this situation is that the extra columns
actually bars of various widths arranged such that
they all of the same heights.
It's not clear how to extend that concept into two dimensions. I imagine
there's research on this though. What do the GIST statistics functions store?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
any further ahead. Doesn't it just move
the problems you have now with the original_expression to flag_var instead?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-hackers mailing list (pgsql
the Append node have had to do some magic to
map the columns correctly meaning you wouldn't be looking at the physical
tuple any more?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list
exclusive partitions is
that there's still a place for this even once we have a more mature
partitioning scheme.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
This file was moved lo, these many years
Done ... but why did your patch change oidjoins.out and not oidjoins.sql?
I had other changes in my tree, I just diffed the files individually rather
than doing a cvs diff
/make_oidjoins_check
--
SELECT ctid, aggfnoid
FROM pg_catalog.pg_aggregate fk
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
of printing a message though -- we should
just have it print the correlation for now and when we improve the stats we'll
print the new metric.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-hackers
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
I agree with that. I like the idea of printing a message though -- we should
just have it print the correlation for now and when we improve the stats
we'll
print the new metric.
Short of actually running an ANALYZE
Josh Berkus [EMAIL PROTECTED] writes:
So it sounds like intagg is still in use/development. But ... is it
more of an example, or is it useful as a type/function in production?
Based on the patch submitted it's definitely in heavy production use.
--
Gregory Stark
EnterpriseDB
a more secure one.
Do salts have to be secure at all? I thought they just had to be widely
distributed so that you couldn't use a dictionary attack. The traditional way
to pick crypt salts for /etc/passwd was to use the first two letters of the
username after all.
--
Gregory Stark
EnterpriseDB
Robert Haas [EMAIL PROTECTED] writes:
CREATE AGGREGATE array_accum (anyelement)
CREATE OR REPLACE FUNCTION array_enum(anyarray)
Have you actually tried these functions on large data sets? They're not in the
same performance league as intagg. Your array_accum is O(n^2)!
--
Gregory Stark
it
and integrate that functionality into the base array operations.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
=0x8484428) at main.c:188
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
was
table_ref RECURSIVE JOIN join_qual)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
. I don't
see why not but it seems fragile.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
This crashes, apparently it tries to look up the result type on a NULL
planstate:
with recursive z(i) as (
select *
from t
union all
(with a(i) as (select * from z)
select * from
Heikki Linnakangas [EMAIL PROTECTED] writes:
Does postgresql support block nested loop join?
Nope.
We do support Hash Join though so I think the only difference is that we can't
use the hash join for cartesian joins.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
join of
two large tables where neither fits in RAM. That does seem like it might be
kind of narrow given how large the output would be.
But we won't know unless someone does the experiment.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony
://www.seagate.com/docs/pdf/datasheet/disc/ds_cheetah_15k_6.pdf
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
Gregory Stark [EMAIL PROTECTED] writes:
For Server Drives 3-4ms are more realistic ([2], [3]) for average seeks and
the 110-170MB/sec are highly exaggerated.
In that case both of those numbers come straight from Seagate's data sheet for
their top-of-the-line data centre drives:
http
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
So the use case of a real block nested loop would be doing a cartesian join
of
two large tables where neither fits in RAM. That does seem like it might be
kind of narrow given how large the output would be.
Yeah
experience doesn't match mine. On a machine with a sizable
raid controller setting random_page_cost higher does generate, as expected,
plans with more bitmap heap scans which are in fact faster.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS
that i/o parameters should be per-tablespace I think
we might need to refactor this further.
I wonder if we could piggy-back on guc parameters. So you would register a guc
variable with a flag saying it's sensible to be set per-tablespace or
per-table.
--
Gregory Stark
EnterpriseDB
to just check if we're inside a non-recursive
WITH without bothering to check if the name matches?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
12345_fsm.1 like we do now but with the symbolic name.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
some or all call sites. I'm not sure we have enough information early
enough to make the decision though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsql-hackers mailing list
issue of conflicts. The
best option right now would be to set aside a range of values for private
purposes.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers
in the CRC checksum should be.
Doesn't the problem still remain? The problem being that the buffer
can be changed as it's written, yes?
It's even worse than that. Two processes can both be fiddling hint bits on
different tuples (or even the same tuple) at the same time.
--
Gregory Stark
of the
full_page_write WAL + WAL changes get us back to the page as it was
before the buffer+checksum+write?
Hint bit setting doesn't trigger a WAL record.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via
a sequential scan does.
And you can't even just set the bits to their correct values either before
the checksum or before checking the checksum since the correct value changes
over time. By the time you compare the checksum more bits will be settable
than when the page was stored.
--
Gregory Stark
Simon Riggs [EMAIL PROTECTED] writes:
On Mon, 2008-09-22 at 16:46 +0100, Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I'd prefer to set this as a tablespace level storage parameter.
Sounds, like a good idea, except... what's a tablespace level storage
parameter
someone setting the hint bits during i/o anyways.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Aidan Van Dyk [EMAIL PROTECTED] writes:
* Gregory Stark [EMAIL PROTECTED] [081001 11:59]:
If setting a hint bit cleared a flag on the buffer header then the
checksumming process could set that flag, begin checksumming, and check that
the flag is still set when he's finished.
Actually I
either.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
as the CRC+copy is carefully written to copy whole atomic-sized
words/bytes and only read the original once then it won't matter if it catches
the hint bit before or after it's set. The CRC will reflect the value buffered
and eventually written.
--
Gregory Stark
EnterpriseDB http
, or the
usable in the sense of larger than the average allocation size
measurements. They're both interesting but not as critical as the bottom-line
number which is how much of the table is being occupied by dead space.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
with that?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
parsetrees would be tough too).
Well the alternative to direct pointers is as you did with subqueries, turning
the set into a flat array and storing indexes into the array. I'm not sure if
that applies here or not.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
Greg Smith [EMAIL PROTECTED] writes:
On Mon, 22 Sep 2008, Gregory Stark wrote:
Hm, I'm disappointed with the 48-drive array here. I wonder why it maxed out
at only 10x the bandwidth of one drive. I would expect more like 24x or more.
The ZFS RAID-Z implementation doesn't really scale
: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
the cursor do they? In
which case it's possible for there to be toast pointers in the cursor which
will expanded much later. If someone else has run CLUSTER in the intervening
time the user will get an error.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
of resources. At this point we only have results from a
few systems and the results don't seem to jibe with the theory.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers
. Or worse, set to a different plugin.
The easiest way to fix this seems like also the best way, instead of storing a
boolean store the pointer to the release function.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent
?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
set in stone doesn't change their decision-making process.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
never increment or decrement just wait until we release all locks at the end
of transaction?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
(and
even mark them invalid).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
with the
plugins available. Worse, there's a risk you could have a plugin but not the
*right* plugin. Perhaps this could be tackled simply by having startup insert
a record listing all the rmgr's in use with identifying information and their
version numbers.
--
Gregory Stark
EnterpriseDB http
site will be getting these
warnings -- and there are a lot of them. Enough that it looks like something's
gone wrong with the build.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list
to configure a maximum amount of time it can be
stalled before shooting those queries.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Simon Riggs [EMAIL PROTECTED] writes:
Indexes have always been able to be added dynamically. Now they can be
recovered correctly as well.
Hm, so currently if you want to add a new indexam you can't just insert
database if you've installed a new version of the plugin since
the standby was built.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
text description and version number to compare.
And as Tom points out startup isn't often enough. Would WAL headers even be
often enough? We would have to ensure there was never two versions of the
plugin in the same WAL file.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
be. A detail line could include the
Postgres-specific authentication method which failed.
I do think it's true that the pg_hba setup is far more complex than it has to
be and that that's a bigger problem than a simple error message too.
--
Gregory Stark
EnterpriseDB http
from those tables and updated other
tables based on that data though. Perhaps there's a solution for that too
though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers
there
aren't exceptions. I don't like the idea of a massive cleanup patch for this
but if someone's doing major surgery on a module it could be worth fixing up
names in that module to be consistent at the same time.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
201 - 300 of 1641 matches
Mail list logo