Re: [PATCHES] patch implementing the multi-argument aggregates (SOC project)

is generally encouraged. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

Re: [PATCHES] Trivial patch to double vacuum speed on tables with no indexes

that it doesn't seem like a concern. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so

Re: [HACKERS] [PATCHES] Trivial patch to double vacuum speed on tables with no indexes

= MaxHeapTuplesPerPage; + } vacrelstats-num_dead_tuples = 0; vacrelstats-max_dead_tuples = (int) maxtuples; -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our

Re: [PATCHES] Concurrent connections in psql patch

and make sure there are no other details like that. It would be nice to get feedback from other developers from looking at the patch to confirm that there aren't more fundamental problems with the approach and how it uses libpq before I go through the effort of cleaning up the details. -- Gregory

Re: [HACKERS] [PATCHES] Trivial patch to double vacuum speed on tables with no indexes

it to acquire a different lock on the same buffer but it's true that it doesn't always have to acquire the second lock. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0

[PATCHES] Some editing of docs for create index concurrently

for unacceptably ! long periods for a production system. /para para -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http

[PATCHES] More doc patches

' ); ALTER TABLE measurement_y2006m02 INHERIT MEASUREMENT; /programlisting /para +sect2 id=ddl-partitioning-caveats para ! The following caveats currently apply to partitioned tables: itemizedlist listitem para -- Gregory Stark EnterpriseDB http

Re: [PATCHES] More doc patches

I did it differently here, weird. Sorry about that. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command

Re: [HACKERS] [PATCHES] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN

implementation details outside the type. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's

Re: [HACKERS] [PATCHES] WAL logging freezing

something clever can be done with vacuum_cost_delay and commit_siblings. Something like inserting the delay between WAL logging and syncing the log and writing to the heap. So if another transaction commits in the meantime we can skip the extra fsync and continue. -- Gregory Stark EnterpriseDB

Re: [HACKERS] [PATCHES] Enums patch v2

the database should take care of this for you anyways. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http

Re: [PATCHES] WIP patch for operator families

discussion should happen on -hackers so development progress would be more visible? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http

[PATCHES] Assorted typos

in pg_attribute.h -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

Re: [pgsql-patches] [HACKERS] [PATCHES] wal_checksum = on (default) | off

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: What did you think about protecting against torn writes using id numbers every 512 bytes. Pretty much not happening; or are you volunteering to fix every part of the system to tolerate injections of inserted data

Re: [pgsql-patches] [HACKERS] [PATCHES] wal_checksum = on (default) | off

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Pretty much not happening; or are you volunteering to fix every part of the system to tolerate injections of inserted data anywhere in a stored datum? I was thinking to do

Re: [pgsql-patches] [HACKERS] [PATCHES] wal_checksum = on (default) | off

the tags would be inserted on the fly as the data was copied into kernel space. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire

Re: [pgsql-patches] Recalculating OldestXmin in a long-running vacuum

. As the table grows the indexes will grow as well and that will slow vacuum down. Though indexes are usually smaller than tables. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched

[PATCHES] WIP: Recursive Queries

of types for $n parameter symbols */ int p_numparams; /* allocated size of p_paramtypes[] */ int p_next_resno; /* next targetlist resno to assign */ -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

[PATCHES] LIMIT/SORT optimization

Description: Binary data -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so

[PATCHES] [test]

[testing to see if -patches allows me to post yet. I send a patch last night but haven't seen it come through] -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through

[PATCHES] Short varlena headers

exempted which only leaves us with the occasional text attribute which I plan to double check aren't problems. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL

[PATCHES] 1-byte packed varlena headers

by heap_form*tuple. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

[PATCHES] Numeric patch to add special-case representations for 8 bytes

how much space is saved for integers 1. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

[PATCHES] Updated Packed Varlena (relative to CVS post SET_VARSIZE changes)

to be varlenas and which are just random C data structures. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

Re: [PATCHES] Numeric patch to add special-case representations for 8 bytes

better. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PATCHES] Numeric patch to add special-case representations for 8 bytes

. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PATCHES] A little COPY speedup

serious. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PATCHES] A little COPY speedup

the others (comma separated and (egads) *pipe* separated?!) are just disasters. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [PATCHES] Heap page diagnostic/test functions (WIP)

of tricky to cons up though. I had to create a table to do it here. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

[PATCHES] Packed Varlenas update

. Fixed all regressions in contrib (gist indexed) modules . Fixed a bug that occurs when a compressed datum ends up under 128 bytes . Fixed a bug on zero-column tuples . Added regression tests http://community.enterprisedb.com/varlena/patch-varvarlena-16.patch.gz -- Gregory Stark

[PATCHES] Updated packed varlena patch

support and changed them to have attstorage 'm' instead. http://community.enterprisedb.com/varlena/patch-varvarlena-17.patch.gz -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0

[PATCHES] non-recursive WITH clause support

written as subqueries. We'll have to do something much more clever to get recursive queries to work but for non-recursive queries that's sufficient. Example: postgres=# with a as (select 1 as x) select * from (select * from a) as x; x --- 1 (1 row) -- Gregory Stark EnterpriseDB http

Re: [PATCHES] WIP patch for plan invalidation

Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Comments? Why do CREATE/DROP/REINDEX DATABASE no longer call PreventTransactionChain? sigh, nevermind. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end

[PATCHES] Packed varlena patch update

convenient way to make something which after compressing was large enough to toast externally. It might be better to find some less compressible data. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP

Re: [PATCHES] guc patch: Make variables fall back to default values

it? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [PATCHES] guc patch: Make variables fall back to default values

. There are about half a dozen Assert(variable-vartype == PGC_STRING) throughout the patch. That's not true, plperl's use_strict is a boolean and we have DefineCustome*Variable functions for each type of variable. Perl bombs because plperl.use_strict is a boolean. -- Gregory Stark EnterpriseDB

[PATCHES] Updated Packed Varlena patch v20 (final?)

with the new macros, for instance. But I want to see what happens when it gets reviewed before I do that kind of bookkeeping. One thing that I've left in there again is the htonl/ntohl macros in the big-endian case. It really makes sense to either remove them or remove the #ifdef. -- Gregory Stark

Re: [PATCHES] LIMIT/SORT optimization

into account the optimization Whether the communication between the Limit node and the Sort node is kosher or whether something more abstract is needed. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2

Re: [PATCHES] LIMIT/SORT optimization

Gregory Stark [EMAIL PROTECTED] writes: Bruce Momjian [EMAIL PROTECTED] writes: Is there a newer version of this patch? As requested, I've cut an updated version of this patch against CVS HEAD: http://community.enterprisedb.com/sort-limit-v5.patch.gz Someone asked why I've been posting

Re: [PATCHES] patch adding new regexp functions

for it though. Do you need the alignment? If so I want to check the code against the packed varlena patch. Just in case. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 7: You can help support

Re: [PATCHES] patch adding new regexp functions

Gregory Stark [EMAIL PROTECTED] writes: Jeremy Drake [EMAIL PROTECTED] writes: BTW, should I be calling get_typlenbyvalalign on TEXTOID or are there macros for those also? Hardcoding -1 for typlen of varlenas is one of the few (the only?) magic constants used throughout the source code

Re: [PATCHES] Improvement of procArray.xmin for VACUUM

and the oldest in-progress transaction. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

Re: [PATCHES] LIMIT/SORT optimization

, that's why we have reviews. Or are you asking if it's ready for someone to look at? What's the point of posting WIP patches if you don't want someone to look at it? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

Re: [PATCHES] Improvement of procArray.xmin for VACUUM

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Well I think this would be the same infrastructure we would need to do the other discussed improvement to address pg_dump's impact. That would require us to publish the youngest xmax of the live snapshots. Vacuum

Re: [PATCHES] Improvement of procArray.xmin for VACUUM

. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PATCHES] Numeric patch to add special-case representations for 8 bytes

it? --- Gregory Stark wrote: I've uploaded a quick hack to store numerics in 8 bytes when possible. http://community.enterprisedb.com/numeric-hack-1.patch This is a bit of a kludge since it doesn't actually provide any interface for external clients of the numeric

Re: [PATCHES] Recalculating OldestXmin in a long-running vacuum

to grow less too but I doubt these tests were long enough to demonstrate that effect. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http

Re: [PATCHES] [PATCH] add CLUSTER table ORDER BY index

anyone name their indexes in a way that would conflict with a column anyways. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [PATCHES] LIMIT/SORT optimization

Heikki Linnakangas [EMAIL PROTECTED] writes: Some comments on the patch below. Thanks! Gregory Stark wrote: The comment claims that we use heap sort when the user says he doesn't want to use glibc's qsort. I recall that we always use our own qsort implementation nowadays. And we never

Re: [PATCHES] LIMIT/SORT optimization

.patch.gz Description: Binary data Gregory Stark [EMAIL PROTECTED] writes: Heikki Linnakangas [EMAIL PROTECTED] writes: There's a few blocks of code surrounded with #if 0 - #endif. Are those just leftovers that should be removed, or are things that still need to finished and enabled? Uhm, I

Re: [PATCHES] Blocked post

Magnus Hagander [EMAIL PROTECTED] writes: Plaintext patch, plus two plaintext .c files. Then I have no clue. Actually I've had more success with .tar.gz than plain text attachments. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end

Re: [PATCHES] Packed Varlena Update (v21)

-bit machine, but probably not for another week. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your

Re: [PATCHES] non-recursive WITH clause support

actually not too sure what the answer is. I hadn't heard of it before the discussion about recursive queries myself. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9

Re: [PATCHES] Packed Varlena Update (v21)

Bruce Momjian [EMAIL PROTECTED] writes: Added to TODO: o Allow single-byte header storage for arrays Fwiw this is single-byte header storage for varlena array *elements* The arrays themselves already get the packed varlena treatment. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] Dead Space Map version 3 (simplified)

... -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [PATCHES] LIMIT/SORT optimization

in stock Postgres to 12s using the bounded heapsort. (Which was an even better result than I had prior to fully randomizing the data. It probably just got packed better on disk in the source table.) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

[PATCHES] updated SORT/LIMIT patch

Updated patch against cvs update in case it makes applying easier. One minor change: . Added #include limits.h in tuplesort.h to pull in UINT_MAX (thanks to dpage for noticing this is necessary on OSX) sort-limit-v8.patch.gz Description: Binary data -- Gregory Stark EnterpriseDB

Re: [PATCHES] updated SORT/LIMIT patch

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Updated patch against cvs update in case it makes applying easier. Applied with revisions --- notably, I avoided adding any overhead to HEAPCOMPARE() by the expedient of reversing the logical sort order before

[PATCHES] Doc and comment patch for packed varlena

)) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

[PATCHES] Concurrent psql patch

like anyone else has any better ideas either. If not then we're going to be stuck with them. More or less, it's explicitly described as an experimental feature in the docs so I suppose we could always change them later. concurrent-psql-v7.patch.gz Description: Binary data -- Gregory Stark

Re: [PATCHES] updated WIP: arrays of composites

is always by foo[] isn't it? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [PATCHES] Concurrent psql patch

have \cs or \cn set up as abbreviations. I was originally thinking \c1, \c2, ... for \cswitch and \c for \cnowait. I'm not sure if going for cryptic short commands is better or worse here. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end

Re: [PATCHES] Concurrent psql patch

does in the shell? Sort of. It sends the *subsequent* command to the background... And unlike the shell you can't usefully do anything more in the current session while the command is in the background, you have to manually switch sessions before issuing subsequent commands. -- Gregory Stark

Re: [PATCHES] Concurrent psql patch

Jim C. Nasby [EMAIL PROTECTED] writes: On Sun, May 13, 2007 at 02:39:45PM +0100, Gregory Stark wrote: I was originally thinking \c1, \c2, ... for \cswitch and \c for \cnowait. I'm not sure if going for cryptic short commands is better or worse here. \c sounds fine (as do \c1...\c9). \g

Re: [PATCHES] Concurrent psql patch

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: David Fetter [EMAIL PROTECTED] writes: What's the reasoning behind \c? Does it send things into the background the way does in the shell? Sort of. It sends the *subsequent* command to the background

Re: [PATCHES] [DOCS] OS/X startup scripts

essential to use rsync to maintain a local CVS repository. That makes 'cvs diff' remarkably fast. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map

Re: [PATCHES] [DOCS] OS/X startup scripts

is to manually edit the Entries files to list the new files. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs

Re: [PATCHES] Concurrent psql patch

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: So would you prefer \g as Jim Nasby suggested? I hadn't even considered that previously since I'm not accustomed to using \g but it does seem kind of pretty. I normally use ; but I suppose there's nothing wrong

Re: [PATCHES] Concurrent psql patch

named 1 today but switch sessions tomorrow. Or we treat it as the first argument in which case even \c 9 switches to session 9. I would prefer to do that but I fear there may be people with databases named 9. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] Concurrent psql patch

. That said, I think a next step for this for interactive use would be to handle C-z to background the currently running query. So perhaps it does make sense to keep use cases like that when deciding on command names now. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] updated SORT/LIMIT patch

whether random access is possible and how many tuples were actually kept. Then nodeSort could ask it those values instead of just remembering what values were requested. sortlimit-fix-v2.diff.gz Description: Binary data -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] updated SORT/LIMIT patch

Alvaro Herrera [EMAIL PROTECTED] writes: Gregory Stark wrote: Attached is a small patch which fixes this case. It also makes the check slightly more liberal -- we don't need to resort if the previous sort was unbounded or the bound was greater than or equal to the new bound. Huh, can you

Re: [PATCHES] [DOCS] OS/X startup scripts

. It doesn't matter, diffs can contain arbitrary junk between the file diffs. patch only looks at the things it recognizes. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9

Re: [PATCHES] Concurrent psql patch

Description: Binary data -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PATCHES] updated SORT/LIMIT patch

but then it's the same inevitable wart as set_bound. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

Re: [PATCHES] updated SORT/LIMIT patch

Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: This patch makes what was already a hack into a full-fledged crock (and it's not just the self-doubting comments that make me distrust it). I think we need to rip out this ad-hoc parameter change signaling code

Re: [PATCHES] CREATE TABLE LIKE INCLUDING INDEXES support

takes a list of column names, full stop. Does the SQL spec actually specify what happens if you provide an non-compliant table definition like this? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP

Re: [PATCHES] Concurrent psql patch

Andrew Dunstan [EMAIL PROTECTED] writes: Gregory Stark wrote: Attached is an updated patch. This patch appears to add a nonexistent test to the regression schedules. I must have forgotten to cvs add it. Sorry. Also, I forgot to mention previously there is an unrelated trivial hunk in here

Re: [PATCHES] cluster test

costs? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your

Re: [PATCHES] Seq scans status update

). Is there a reason UnpinBuffer has to be the one to increment the usage count anyways? Why can't ReadBuffer handle incrementing the count and just trust that it won't be decremented until the buffer is unpinned anyways? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] Concurrent psql patch

into psql? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [PATCHES] Concurrent psql patch

distracted by some tests I've been running. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

[PATCHES] Bug in date.c

textout when the error is thrown. Alternatively it might be handy to have a custom escape in errmsg format strings for text varlena data. date.c.patch.gz Description: Binary data date-minimal.c.patch.gz Description: Binary data -- Gregory Stark EnterpriseDB http

Re: [PATCHES] Synchronized scans

position which i would expect would be pretty rare except for the last scanner. If a backend died it would leave a scan position behind but the next scanner on that table would overwrite the pid and then remove it when it's finished. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] Synchronized scans

the sleep time was so large that the other scans managed to cycle through the entire ring in that time. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet

Re: [PATCHES] Synchronized scans

when it goes to reuse them. Effectively we'll have just reinvented the problem we had with vacuum previously albeit in a way which only hits sequential scans particularly hard. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

[PATCHES] Two aesthetic bugs in the 1-byte packed varlena code

flatfiles.c-minimal.gz Description: Binary data inv_api.c-fastgetattr.gz Description: Binary data -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map

Re: [PATCHES] Two aesthetic bugs in the 1-byte packed varlena code

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Why do we even have those fields in the structs if they're unsafe to use? 1. genbki.sh But genbki.sh wouldn't care if we #if 0 around the unsafe ones would it? 2. As you note, they're not always unsafe to use. Well

Re: [PATCHES] Two aesthetic bugs in the 1-byte packed varlena code

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: The other instance is in inv_api.c where it would be quite possible to use fastgetattr() instead. But the column is always at the same fixed offset and again it follows an int4 so it'll always be 4-byte aligned

[PATCHES] Silly bug in pgbench's random number generator

) * (double) random()) / MAX_RANDOM_VALUE); } /* call PQexec() and exit() on failure */ -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating

Re: [PATCHES] Maintaining cluster order on insert

the last block it suggested and somehow recognize when it's given the same tuple to index. Keeping the block pinned would still be the sticky point though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

Re: [PATCHES] [HACKERS] 'Waiting on lock'

at this I found that the early deadlock detection never seems to fire. Reading the source it seems it ought to be firing whenever we have a simple two-process deadlock. But instead I only get the timeout-based detection. checkpoint-log-messages-fix.patch.gz Description: Binary data -- Gregory

Re: [PATCHES] [HACKERS] 'Waiting on lock'

Gregory Stark [EMAIL PROTECTED] writes: Incidentally in looking at this I found that the early deadlock detection never seems to fire. Reading the source it seems it ought to be firing whenever we have a simple two-process deadlock. But instead I only get the timeout-based detection. Ok, I

Re: [PATCHES] [HACKERS] 'Waiting on lock'

regression tests. I suppose having the pids already interferes with regression tests though. Maybe we should do something like optionally postprocess .out files with some sed script like s/[0-9]+/###/ before running diff. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] [HACKERS] 'Waiting on lock'

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Is it possible for unlocking the semaphore to wake another process other than our own? In which case checking log_lock_waits before signalling the semaphore arguably locks us into having log_lock_waits

Re: [PATCHES] [HACKERS] 'Waiting on lock'

Tom Lane [EMAIL PROTECTED] writes: Which is always the same process: PGSemaphoreUnlock(MyProc-sem); Aaah! I just grokked what's going on with the semaphores here. It all makes a lot more sense now. Nevermind. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] Load Distributed Checkpoints, final patch

that the next checkpoint starts. Aside from it not actually helping is there much reason to avoid this situation? Have we ever actually tested it? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3

Re: [PATCHES] Load Distributed Checkpoints, take 3

pages that it could have flushed out during the idle time. Effectively you're only making use of half the i/o bandwidth since bgwriter doesn't do any work for half the duty cycle. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

Re: [PATCHES] dblink connection security

to the PUBLIC role by default as other packages typically do. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

Re: [PATCHES] dblink connection security

to circumvent. That sentence is too generous of a promise. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

  1   2   3   >