[HACKERS] date_part()/EXTRACT(second) behaviour with time data type

date_part --- 27.782458 (1 row) -- Gregory Stark http://mit.edu/~gsstark/resume.pdf -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Merge Append Patch merged up to 85devel

List *tidquals); -extern AppendPath *create_append_path(RelOptInfo *rel, List *subpaths); +extern AppendPath *create_append_path(PlannerInfo *root, + RelOptInfo *rel, + List *subpaths, + List *pathkeys); extern ResultPath *create_result_path(List *quals); exter

[HACKERS] Merge Append Patch merged up to 85devel

List *tidquals); -extern AppendPath *create_append_path(RelOptInfo *rel, List *subpaths); +extern AppendPath *create_append_path(PlannerInfo *root, + RelOptInfo *rel, + List *subpaths, + List *pathkeys); extern ResultPath *create_result_path(List *quals); exter

Re: [HACKERS] Plan time Improvement - 64bit bitmapset

Andres Freund writes: > Plan time (averaged) without change: > cnt: 40 (4 times per session) > avg: 4572ms > > Plan time (averaged) with change: > cnt: 40 (4 times per session) > avg: 4236ms > > ~7% difference. Same with higher number of repetitions and with most other > planner settings I tried

Re: [HACKERS] postmaster recovery and automatic restart suppression

switch, or various other options. Gregory Stark http://mit.edu/~gsstark/resume.pdf -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Plan time Improvement - 64bit bitmapset

that can get big pretty quickly. But that doesn't explain the bitmap ops being important. Hm. Actually having a lot of columns and then joining a lot of tables could mean having fairly large bitmapsets. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about En

[HACKERS] valgrind errors

E3597: ExecutePlan (execMain.c:1504) ==20253==by 0x81E16F3: standard_ExecutorRun (execMain.c:309) ==20253==by 0x81E15A4: ExecutorRun (execMain.c:258) ==20253==by 0x82CD9E5: ProcessQuery (pquery.c:196) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about Enterpris

[HACKERS] valgrind error in tsvectorin

) ==19366==by 0x8174B01: transformTargetList (parse_target.c:145) After a quick glance at the code I suspect res and ptr end up pointing to the same object, perhaps the loop condition has a fencepost error. But I don't really understand what it's trying to do at all. -- Gre

Re: [HACKERS] Serializable Isolation without blocking

ntial records which might be inserted in the future? -- 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

Re: [HACKERS] [PATCH] unalias of ACL_SELECT_FOR_UPDATE

privileges from users to make these programs ineffective? So even if you obtain root privileges you're missing the SE privilege which the program expects to use? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! --

Re: [HACKERS] Unicode support

TF8 encoding required normalizing the string of unicode codepoints before encoding. I'm not sure that's true though, is it? -- 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

[HACKERS] Strange query plan with redundant aggregate nodes

.01 rows=1 width=0) -> Seq Scan on a (cost=0.00..2588.00 rows=10 width=0) -> Aggregate (cost=2838.00..2838.01 rows=1 width=0) -> Seq Scan on a (cost=0.00..2588.00 rows=10 width=0) -> Result (cost=0.00..0.01 rows=1 width=0) (7 rows) -- Gregory Star

[HACKERS] Translation conventions

n list is required for functions returning \"record\"" ./po/fr.po:7752:msgid "a column definition list is required for functions returning \"record\"" ./po/hr.po:4902:msgid "a column definition list is required for functions returning RECORD" -- Gregory

Re: [HACKERS] default parameters for built-in functions

7;s really quite a pain to maintain these files manually, especially pg_operator. -- 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 cha

Re: [HACKERS] small but useful patches for text search

27;m only interested in when features get committed, not when they hit a release. But in any case I think experience shows that this would result in hitting the same release anyways and that release would be sooner as well. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask m

Re: [HACKERS] Has anybody think about changing BLCKSZ to an option of initdb?

ource. Heck the only time I compile from source is > when I need to fix mis-configured defaults in RH packages (which is why > we now have rpms that fix those defaults) or when we have back patched > something for a customer. So has anyone here done any experiments with live systems wit

Re: [HACKERS] Should SET ROLE inherit config params?

gt; It solves a problem mentioned by Tom as it's very clear that it's a > new session so when you reset the settings to what they were at > session start, you take the default settings of special. So this is just syntactic sugar for SET ROLE; RESET ALL; Or is it

Re: [HACKERS] Updates of SE-PostgreSQL 8.4devel patches (r1710)

dually at a later date? That might relieve critics of the sneaking suspicion that there may be some semantic change that hasn't been identified and discussed and snuck through? Some of them are probably good ideas but if they are they're probably good ideas even for non-SE semantics

Re: [HACKERS] Updates of SE-PostgreSQL 8.4devel patches (r1704)

for example a client that has a capability that allows him to read a file can pass that capability to the server and be able to use COPY to read it directly on the server. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!

Re: [HACKERS] Potential problem with HOT and indexes?

Tom Lane writes: > Gregory Stark writes: >> Another thought now though. What if someone updates the pg_index entry -- >> since we never reset indcheckxmin then the new tuple will have a new xmin and >> will suddenly become invisible again for no reason. > > Hmm

Re: [HACKERS] Potential problem with HOT and indexes?

Tom Lane writes: > Gregory Stark writes: >> So it occurs to me that freezing xmin won't actually do what we want for >> indexcheckxmin. Namely it'll make the index *never* be used. > > How do you figure that? FrozenXID is certainly in the past from any > vant

[HACKERS] Potential problem with HOT and indexes?

ains. Currently, we set this if there are > * any RECENTLY_DEAD entries in a HOT chain, without trying very hard to > * detect whether they're really incompatible with the chain tip. I wonder if this particular case is good evidence that we need to be cleverer about checking if th

Re: [HACKERS] Out parameters handling

e only way we could get it right is if we default to the local variable but only in contexts where an expression is valid. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers m

Re: [HACKERS] TOAST table (or index?) corruption on PITR replica

ues. Do you know how big this table was when the backup was taken? Were these blocks present then or were they added since then? My suspicion would lie with the relation extension code where there have been bugs before, but I don't see any found recently. -- Gregory Stark EnterpriseDB

Re: [HACKERS] Validating problem in the isn contrib module

iour or just a > bug? And how can one validate an ISBN without raising an error? -- 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 c

Re: [HACKERS] Validating problem in the isn contrib module

before the validator function ever gets a chance to act. The validator function receives an already-formed isbn13 datum. Is there an is_valid() which takes text input? Perhaps there should be -- though I think it would have to be isbn_is_valid() or something like that. -- Gregory Stark

Re: [HACKERS] cardinality()

Peter Eisentraut writes: > The standard represents multidimensional arrays as arrays of arrays (like in > C). Uh, C doesn't represent multidimensional arrays as arrays of arrays so you've lost me already. -- Gregory Stark EnterpriseDB http://www.enterprisedb.co

Re: [HACKERS] would it be a lot of work, to add optimizations accross unions ?

Grzegorz Jaskiewicz writes: > On 28 Feb 2009, at 11:37, Gregory Stark wrote: >> >> I posted a patch to look for an ordered path for members of a union a while >> back but it still needed a fair amount of work before it was usable. >> > I belive limit it self can&#x

Re: [HACKERS] would it be a lot of work, to add optimizations accross unions ?

rk if there are no conditions on there append path.) And I believe we already do push down where clauses like foo=N. > Same would actually apply for different subqueries, without union/ > intersect/etc: > > select foo( select foo from bar1 ) a where foo in (x,y,z) order by foo desc &

Re: [HACKERS] Adding a field in Path Structure and Plan Structure

. Though if you have the backend crashing on every plan it may not help... -- 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 t

Re: [HACKERS] pgsql: Add quotes to message

OidIsValid(returned->attrs[i]->atttypid) ? format_type_be(returned->attrs[i]->atttypid) : _(dropped_column_type), I'm surprised there isn't a regression test for this case. -- Gregory Stark Ent

Re: [HACKERS] Multi calendar system for pgsql

NT32. I removed all palloc calls. but the server > crashes with segmentation fault before returning in pdate_in. You want to set PASSEDBYVALUE (And you probably want to adjust alignment though I don't think it's causing any problem aside from wasted space) -- Gregory Stark

Re: [HACKERS] WIP: hooking parser

which is the same as '') What's more puzzling is what the answer to 'foo' || NULL is... -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-

Re: [HACKERS] graph representation of data structures in optimizer

l of a lot harder to read. I'm not sure how to do any better but I would be fascinated to see any new images you generate :) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list

Re: [HACKERS] pg_migrator progress

Tom Lane writes: > Gregory Stark writes: >> Also I wonder about the performance of skipping over thousands or even >> millions of OIDs for something like a toast table. > > I think that argument is a red herring. In the first place, it's > unlikely that there&#

Re: [HACKERS] pg_migrator progress

of skipping over thousands or even millions of OIDs for something like a toast table. -- 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

Re: [HACKERS] [BUGS] BUG #4660: float functions return -0

But without a convenient and widely used binary format that kind of restricts our options. If we squash -0 on float[48]out then dumps will lose information. So I guess there's nothing we can do about it now. I wonder if we're going to find users complaining about things like "displ

Re: [HACKERS] SE-PostgreSQL and row level security

ge to the SQL semantics where every query effectively has a volatile function in it which produces different answers for different users. And it doesn't accomplish anything since the covert channels it attempts to address are still open. -- 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/mailpref/pgsql-hackers

Re: [HACKERS] polyphase merge?

er hand possible reasons why filesystems would suck at this include creating and deleting new files being a slow or locking operation on many filesystems, and dealing with directories of large numbers of files being poorly optimized on others. -- Gregory Stark EnterpriseDB http://www.

Re: [HACKERS] Hot Standby (v9d)

the backend to? There could have been several generations of tuples in that tid since your query started. Do you take a snapshot every time there's a vacuum-snapshot conflict and record which snapshot goes with that snapshot? -- Gregory Stark EnterpriseDB http://www.enter

Re: [HACKERS] adding stuff to parser, question

Grzegorz Jaskiewicz writes: > On 31 Jan 2009, at 17:17, Gregory Stark wrote: >> >> I don't see any reason offhand why it should have to be a reserved word >> though. You should be able to make it an UNRESERVED_KEYWORD. Oh, and you'll >> wa

Re: [HACKERS] adding stuff to parser, question

gh. You should be able to make it an UNRESERVED_KEYWORD. Oh, and you'll want to add it to the list of tokens in unreserved_keyword in gram.y as well. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL trai

Re: [HACKERS] [PATCH] Space reservation v02

h as adding columns -- we could clear it from the server side easily. -- 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://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Commitfest infrastructure

d. For what it's worth Google seems to have rolled out reviewboard as a Google App. We could use it hosted on there if we wanted. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mail

Re: [HACKERS] 8.4 release planning

ut testing major features that people haven't already tested outside of development environments. -- 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://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Commitfest infrastructure

ering authors about on-list. But I don't think it really helps with the hard reviews. But that's just a cute tool for one particular part of the work. I don't think it addresses workflow management like RT or debbugs (or trac?) would. -- Gregory Stark EnterpriseDB http://

Re: [HACKERS] How to get SE-PostgreSQL acceptable

ing out loud. I don't have a well-formed idea based on this. -- 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 sub

Re: [HACKERS] How to get SE-PostgreSQL acceptable

different physical places just because our security model is based on the place the data is stored is kind of silly. Unless perhaps we implement partitioning which supports having many partitions share the same underlying, er, physical partition. But then I don't see how that's a

Re: [HACKERS] Hot Standby (v9d)

it. But there are plenty of other use cases. I claim the default has to be to do as the user instructed without intervention. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsq

Re: [HACKERS] How to get SE-PostgreSQL acceptable

he same thing as row-level security. But I wonder if some of the same infrastructure could be used for both -- once we have it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Se

Re: [HACKERS] Hot Standby (v9d)

hose xids are visible or not, blowing a huge hole in MVCC. + * We need 'em. But that doesn't sound rational to me. I'm not sure what "confusion" this would cause. If they later actually complete then any existing snapshots would still not see them. And any later snapshots wo

Re: [HACKERS] 8.4 release planning

ng to be 9+ months between Nov 1st and the first commitfest I'm worried about how many patches will be languishing in the queue with their authors having moved on to other more fruitful pastures in the mean time. If we delay further we're talking about close to a year with developers le

Re: [HACKERS] posix_fadvise v22

ill queued separately from old ones that are probably in cache. And we also have to think about how long to treat prefetches as probably still being in cache. But with some additional thought I think this could be made to work.] -- Gregory Stark EnterpriseDB http://www.enterprisedb.

Re: [HACKERS] Index Scan cost expression

nly compute histograms and use them for selectivity estimates. The challenge in this case is that you need to combine the distribution from the outer node with the distribution in the inner node to estimate how much overlap in disk accesses will result. So you need more than histograms, you need som

Re: [HACKERS] 8.4 release planning

set" on these privileges? Or are they too general for that? And would you have trouble adjusting the privileges later because giving someone access to a label would require checking every row to see if they have access to every referenced row too? -- Gregory Stark EnterpriseDB

Re: [HACKERS] 8.4 release planning

d on Heikki's suggestions as fast as he's been proposing them though. It seems the question isn't how fast Simon will get the work done so much as how many items we'll want to change before committing it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.

Re: [HACKERS] More FOR UPDATE/FOR SHARE problems

he ACM last year, which provides techniques for a more > general and comprehensive solution. Hopefully it's not patent encumbered? Might be better not to check actually. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask m

Re: [HACKERS] Index Scan cost expression

t to be discounted at all, but if it has a subquery which scans a small table it will want to discount that 100% for any repetitions since it'll be cached after the first scan. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand P

Re: [HACKERS] 8SEPostgres WAS: .4 release planning

umentation then either it needs better documentation or something's wrong... -- 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) T

Re: [HACKERS] 8.4 release planning

ul merges into this shared branch would be rare, as the source control > system would remember the painful parts of the merges. We have git repositories, I still think maintaining a merged tree with dozens of patches would be a lot of work. -- Gregory Stark EnterpriseDB http://

Re: [HACKERS] More FOR UPDATE/FOR SHARE problems

finishes. In any case note that your example is not *serializable*. (Though in Postgres it can happen even in serializable mode, so that's not much of a defence.) I'm unclear what whether it manifests any of the phenomenon which are prohibited for READ COMMITTED. -- Gregory Stark En

Re: [HACKERS] 8.4 release planning

velopment cycle I don't believe we would refuse to commit it today if it was ready. And I can't imagine two weeks would make the difference either. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's

Re: [HACKERS] 8.4 release planning

ill be about a month) then we're looking at 3-4 months before 8.4 or about May. I fear that 3-4 months will already be long enough to back up development on 8.5 and cause a big queue for the first commitfest. Frankly, at 3 months I think feature freeze has _already_ gone on too long, I do

Re: [HACKERS] 8.4 release planning

Tom Lane writes: > Gregory Stark writes: >> Put another way, the choice here is whether to have a half-baked delayed 8.4 >> release in 6 months or a polished on-time 8.5 release in 12 months. Either >> way >> the feature ships and on a not terribly different t

Re: [HACKERS] 8.4 release planning

aintainers send up patches for all the changes that have happened since the last cycle that they think are ready for release. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing

Re: [HACKERS] 8.4 release planning

choice here is whether to have a half-baked delayed 8.4 release in 6 months or a polished on-time 8.5 release in 12 months. Either way the feature ships and on a not terribly different timeline either. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about Enterpri

Re: [HACKERS] V4 of PITR performance improvement for 8.4

Koichi Suzuki writes: > It's simply because we should not refer to system catalog during the recovery. I don't understand how this is connected to anything to do with prefetching? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseD

Re: [HACKERS] V4 of PITR performance improvement for 8.4

d such a cache directly to PrefetchBuffer -- in which case it would remember if some other scan prefetched the same buffer -- or to keep it in the index scan code. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning --

Re: [HACKERS] More FOR UPDATE/FOR SHARE problems

mmands on other rows in the database. This behavior makes Read Committed mode unsuitable for commands that involve complex search conditions. However, it is just right for simpler cases. For example, consider updating bank balances with transactions like ... -- Gregory Stark EnterpriseDB

Re: [HACKERS] [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle

pdate a view written inline in the query like: UPDATE (select * from a where x=1) set y=2 just like I can with SELECTs. This does incidentally work in Oracle and is its way of doing what we do with UPDATE...FROM. It's the only way AFAIK to get merge join update plans out of it. -- Gre

Re: [HACKERS] Controlling hot standby

riptive. > > Could also be something like "allow_connections_during_recovery". > > I'd keep the word "replication" out of this.. Just wondering, but does this make more sense as a recovery.conf parameter? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained

Re: [HACKERS] Pluggable Indexes

nnecessary. Well we support pluggable indexes -- they just can't be recoverable right now. Presumably if they're merged into the core database they would have recoverability added like how GIST progressed. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask m

Re: [HACKERS] rmgr hooks (v2)

be specific enough to be useful but general enough to cover all the use cases. I'm not sure though, your comments in the other email make me think there might be more to the patch that I had the impression was there. Will now go read the patch and see if I was mistaken. -- Gregory Stark E

Re: [HACKERS] FWD: Re: Updated backslash consistency patch

quite a bit. I wonder if we could rename all our internal functions which implement operators and indexam methods without introducing any backwards compatibility issues. We don't document things like "int4gt" after all. -- Gregory Stark EnterpriseDB http://www.enterp

Re: [HACKERS] Pluggable Indexes

along with the "plugins" thread. Binary modules could have some way to register their rmgr id so you could guarantee that there aren't two plugins with conflicting rmgr ids or version mismatches. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about E

Re: [HACKERS] Fixes for compiler warnings

n-zero escapes and find something else than to just not think about it at all and unknowingly depend on having no escapes. And it would take willful ignorance to depend on having some specific set of escapes in an unchecked string provided by an external data source, which is where the worst danger lies.

Re: [HACKERS] Fixes for compiler warnings

y too. Even if the current code is correct you have to trace the variable back up to its source to be sure. If you add the escape then you can see that the code is safe just from that line of code alone. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about Enterpris

Re: [HACKERS] MemoryContextSwitchTo (Re: [GENERAL] Autovacuum daemon terminated by signal 11)

t()/restore_memory_context() which gave you more than just a pointer we could do better for this particular case. save_memory_context() could hand you a struct with a pointer as well as some sanity check values about the context you're saving. -- Gregory Stark EnterpriseDB

Re: [HACKERS] FWD: Re: Updated backslash consistency patch

t); CREATE TABLE postgres=# commit; COMMIT postgres=# \dt pg_proc No matching relations found. And I don't see any reason aggregates, operators, etc, shouldn't be any more susceptible the shadowing problem. -- Gregory Stark EnterpriseDB http://www.enter

Re: [HACKERS] Visibility map and freezing

ng of these GUCs in the >> name. I think our goal should be to avoid confusion between them. > > Agreed. I was thinking it would be clearer if the options which control *when* autovacuum fires off a worker consistently had some action word in them like "trigger" or "sta

Re: [HACKERS] Visibility map, partial vacuums

often than necessary. The rest of the thread is visible at the bottom of: http://article.gmane.org/gmane.comp.db.postgresql.devel.general/107525 > Also, is anything being done about the concern about 'vacuum storm' > explained below? I'm interested too. --

Re: [HACKERS] Updates of SE-PostgreSQL 8.4devel patches (r1403)

now that's not an issue? It > seems a shame to have to do palloc/pfree in a situation like this. palloc really isn't that expensive, unless you're allocating tons of tiny objects or you're in a tight loop it's not worth worrying about. -- Gregory Stark EnterpriseDB

Re: [HACKERS] A single escape required for log_filename

ties. Debian's priorities are generally to have all packages behave in consistent ways. In particular it's very useful to be able to guarantee that all log files will go to the same place and be governed by a single set of policies defined in a single place. -- Gregory Stark En

Re: [HACKERS] [BUGS] Status of issue 4593

ed by rewriting the application to not cause deadlocks. -- 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 chang

Re: [HACKERS] Recovery Test Framework

#x27;t know how much real work it removed from Tom's plate but I suspect it did reduce the little annoyances significantly. > In my mind though, the real benefit of the system and the reason we > should keep it up is to get more people looking at the code. New > committers don'

Re: [HACKERS] Open item: kerberos warning message

t;> support for this. Users can always use -U (or equiv) if necessary. > > I have applied this version of the patch. yay! Incidentally, this will have to be in the update notes I think. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momj

Re: [HACKERS] Recovery Test Framework

r tweaks and refinements are worth bothering with. Any thoughts of continuing on any subsequent phases of development are all crushed since all that work might go down the drain when the committer makes changes to the code it's based on. -- Gregory Stark EnterpriseDB ht

Re: [HACKERS] Patch for str_numth() in PG 7.4

gettext_noop("Ctype")); > ! appendPQExpBuffer(&buf, > ! " d.datacl as \"%s\"", > gettext_noop("Access Privileges"))

Re: [HACKERS] Recovery Test Framework

there are better ways to do things doesn't mean the current code isn't acceptable. -- 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 (pgs

Re: [HACKERS] pgsql: Tweak order of operations in BitmapHeapNext() to avoid the case

ore we consider issuing a > prefetch. Doesn't this break things if, say, there's precisely one tuple on every page? You'll keep raising the prefetch_target but never actually prefetch anything. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get traine

Re: [HACKERS] Sample of user-define window function and other things

27;t support it. Even if they can support it shouldn't they reject functions that aren't actually window functions? What happens if you mark a perfectly normal function as a window function, does it behave sanely? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [HACKERS] [BUGS] Status of issue 4593

o, but I figured I would throw it out there in case it gives anyone an idea. -- 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/mailpref/pgsql-hackers

Re: [HACKERS] Recovery Test Framework

in the patch. They don't affect the run-time behaviour and I love the fact that they might turn up any problems with our existing recovery process. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent v

Re: [HACKERS] about truncate

nt INFO messages when drops cascade. We could print similar messages when DDL applies recursively by default. (We can't do DML since it would fill logs quickly). That seems reasonable to me. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Rem

Re: [HACKERS] posix_fadvise v22

ve_io_concurrency to zero disables > prefetching altogether; there was no way to do that in the patch as > submitted. Hm. the original intent was that effective_io_concurrency 1 meant no prefetching because there was only one drive. I wonder if that worked earlier and got lost along the way or

Re: [HACKERS] posix_fadvise v22

index tuples. So I think we would still want to pause when we hit the end of the current leaf page. That would require some form of feedback in the index am api as well. -- 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://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] pgsql: Re-enable the old code in xlog.c that tried to use

uld just be HAVE_POSIX_FADVISE not USE_POSIX_FADVISE. The latter was the define I made if the run check passed. -- 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

Re: [HACKERS] [PATCHES] updated hash functions for postgresql v1

But I gather it's a 6% speedup in the time spent actually in the hash function. Is that really where much of our time is going? If it's 10% of the total time to execute one of these nodes then we're talking about a 0.6% optimization... -- Gregory Stark EnterpriseDB http://ww

Re: [HACKERS] Buffer pool statistics in Explain Analyze

ared buffers, filesystem cache, and physical reads. -- 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/mailpref/pgsql-hackers

Re: [HACKERS] QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows)

#x27;s all spaces we don't try to compress it at all. But if you added one more attribute we would go to great lengths compressing and storing attributes externally -- not necessarily the attribute you just added, the ones that were perfectly fine previously -- to try to get it un

  1   2   3   4   5   6   7   8   9   10   >