tely see is that it uses threads.
--
Jeff Trout
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Dec 4, 2009, at 6:18 AM, Tim Bunce wrote:
- generalize the Safe setup code to enable more control.
Is there any possible way to enable "use strict;" for plperl (trusted)
modules?
I would love to have that feature. Sure does help cut down on bugs and
makes things nicer.
e bottom).
I think my confusion came up because I'd read the trust/untrusted
thing which removes the ability to use use/require.
Maybe a blurb or moving that chunk of doc to the trusted/untrusted
page might make that tidbit easier to find?
--
Jeff Trout
http://www.stuarthamm.net/
http://ww
ng in we think we'll
need to deal with it and not worry about the retroactive case (unless
someone has a really clever(tm) idea!)
This can't be an original problem to solve, too many other databases
do it as well.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.stuarthamm
ar into it but I figured (func()).* was being
expanded by the parser into func().a, func().b and friends. marking it
stable didn't help.
It can be quite surprising, especially if func() is expensive (as was
my case) or has side effects.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www
ue ID that could be used for a lookup key. This puts a bit
of a
Wouldn't the tid fit this? or table oid + tid?
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
at the bottom "ERROR: syntax error at line 2658: unexpected
token parse error". It seems like this is complaining about the
syntax of line 2658 in the postgres.bki file, but I don't see any
problem with the syntax here.
Does anyone have any ideas about the problem here?
Than
es - hte fact pg "just
works" and the tunability of bigger db's (Oh yeah - and we've actually had
informix on the horn about the problem - their solution was "upgrade to
9.4 - it'll be out in march").
Hopefully this last thing will complete and I'll be done with
nd have the client ask for the details if
it wants it.
--
Jeff Trout <[EMAIL PROTECTED]> http://www.jefftrout.com/
Ronald McDonald, with the help of cheese soup,
c
one have lists of implementation-defined SQLSTATEs for
> the big commercial DBs?
>
On informix SQLSTATE is mostly for getting the oh.. lets call it the
"genre" of the error. They use a separate error code which contains the
specific error.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.j
ke
that...
(for the record, the fragment types are round robin and expression. You
can fragment based on a limited-edition where clause.. )
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---(end of broadcast)
user
> "postgres" does not exist
> pg_regress: createdb failed
> make: *** [check] 2
>
simply add the user. in a unix environment, and specifically Red Hat (though
it may apply in other places), you use the 'adduser' program, which has a
good man page.
On Tue, Jul 01, 2003 at 11:09:15PM +0200, Markus Bertheau wrote:
> Subject: Re: [HACKERS] make check fails: user "postgres" doesn't exist
> From: Markus Bertheau <[EMAIL PROTECTED]>
> To: Jeff <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> X-Mailer: Ximian
file
seem more like a device 2. reduce fragmentation 3. guarantee that 2GB
"chunk" can never have an out of space issue.
On a dedicated pg box there is probably not much fragmentation (and thanks
to today's modern filesystems, it isn'ttoo big of a deal in any case)..
but it w
you, give us the table schema and run:
EXPLAIN ANALYZE SELECT * FROM table1 WHERE id=10
and then run:
EXPLAIN ANALYZE SELECT * FROM table1 WHERE id<10
and give us the output.
Then run "VACUUM ANALYZE" every once in a while (depending on how fast your
data changes)
at me strangely and have no
idea about it. You get less of it with contrib/ items..
just my $0.02
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---(end of broadcast)---
TIP 3: if posting/reading throug
ase run it again, this time
with say, 1000 connects. That will give a more true number.
And also try running several of these in parellel.
I've been using pgpool in production with great success and it can
drastically improve connect times.
--
Jeff Trout <[EMAIL PROTECTED]>
http://ww
e new code enough to
see the results?
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---(end of broadcast)---
TIP 8: explain analyze is your friend
ly this will go away if and when Debian releases a new stable
release.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---(end of broadcast)---
TIP 8: explain analyze is your friend
channel.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
r own truely unique type where
you need to write your inputter, outputter and comparison functions.
That can allow you to natively support some proprietary data format you
may have.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
f answer for
multi-master, and I'm curious what it is. If they don't, is it reasonable
to make a test case that leaves their database inconsistent or hanging?
I can (probably) get access to a SQL Server system to run some tests, if
someone is interested.
regards,
jeff
ompiled telling you it will only
run on ultrasparc machines)
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
of swap (swap never touched).
>
Do you have any system monitoring scripts that may be killing it as it
may look like a "runaway" process?
We've had this happen to us before. You tend to forget about things like
that.
--
Jeff Trout <[EMAIL PROTEC
ng to tweak an individual one of those purposes other
> > than CREATE INDEX.
>
I don't know if this would apply here - but foriegn key creation also
benefits hugely from jacking up sort_mem and you also don't do too many
of those in parellel.
I'm guessing it would be qui
.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 16
kern.sysv.shmall: 327680
I've been running PG ith 10k shared bufs for a while.
The pain is sometimes /ec/rc gets rewritten :(
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
-
icate. But plenty of breathing room for normal
operation.
Various db's support in place upgrades. and I'm thankful I tried
Informix's out on a test db first because it simply scribbled over all
the data instead of upgrading. Support told me that can happen
sometimes. COOL HUH?
-
asiest, safest path for a PG
upgrade... in my case the problem is I do have another server with
plenty of room, but it doesn't have much CPU or RAM and cannot handle
the volume of live traffic the master gets. So I have no choice but to
plead my case and ask for some downtime. oh well.
-
. Might as well try to play "good citizen" and talk
with them, perhaps they'll give us some sort of indemnity for 8.0 so we
can get something perhaps better for 8.1.
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---
r the xid wraparound... issuing a NOTICE / ERROR in a new version
will be good, but backpatching won't be needed. As others have said,
the people who really need this are not smart enough to upgrade / watch
for patches / RTFM
--
Jeff Trout <[EMAIL PROTECTED]>
http://www.jefftrout.
s by Simon Riggs
It is not a part of the code-base I'm familiar with, so it is unlikely
I can find the bug.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
] could not execute query: ERROR: function
gtsquery_consistent(internal, internal, integer, oid, internal) does
not exist
Command was: CREATE OPERATOR CLASS "gist_tp_tsquery_ops"
FOR TYPE "pg_catalog"."tsquery" USING "gist" AS
STORAGE bigint ,
Since SSL compression seems to be a busted flush, I would like to see
pg_basebackup be able to do compression on the server end, not just
the client end, in order to spare network bandwidth.
Any comments on how hard this would be, or why we don't want it?
Cheers,
Jeff
--
Sent via
formance bug
fixes which might negatively impact some users. The only times we
have done it that I can think of are when there is almost no
conceivable way it could have a meaningful negative effect, or if the
bug was tied in with security or stability bugs that needed to be
fixed anyway and couldn't be separated.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
lease
> tell me what I'm missing.
I think that this loop:
while (blkend >= end)
Executes exactly twice for each iteration of the outer loop. I'd
rather see it written as a loop which explicitly executes twice,
rather looking like it might execute a dynamic number of times. I
c
dw, I'll look into that when I get a
chance of no one beats me to it.
postgres_fdw.c: In function 'postgresGetForeignJoinPaths':
postgres_fdw.c:3623: error: too few arguments to function
'clauselist_selectivity'
postgres_fdw.c:3642: error: too few arguments to funct
4e48 "regression", username=0x23d4e30 "jjanes") at
postgres.c:4021
#21 0x00745a62 in BackendRun (port=0x23f4110) at postmaster.c:4258
#22 0x007451d6 in BackendStartup (port=0x23f4110) at postmaster.c:3932
#23 0x00741ab7 in ServerLoop () at postmaster.c:1690
On Tue, Mar 8, 2016 at 4:09 PM, Alvaro Herrera wrote:
> Jeff Janes wrote:
>> pgcrypto supports s2k-mode for key-stretching during symmetric
>> encryption, and even defaults to s2k-mode=3, which means configurable
>> iterations. But it doesn't support s2k-count to actual
On Wed, Mar 9, 2016 at 9:21 AM, Tomas Vondra
wrote:
> Hi,
>
> On Wed, 2016-03-09 at 08:45 -0800, Jeff Janes wrote:
>> On Wed, Mar 9, 2016 at 7:02 AM, Tomas Vondra
>> wrote:
>> > Hi,
>> >
>> > thanks for the feedback. Attached is v14 of the pat
weasel words. I think it's hard to talk about
> performance while maintaining the general tone of the documentation. I
> don't know what can be done about that.
Would the wiki be a good place for such tips? Not as formal as the
documentation, and more centralized (and editable) tha
On Wed, Mar 9, 2016 at 9:21 AM, Tomas Vondra
wrote:
> Hi,
>
> On Wed, 2016-03-09 at 08:45 -0800, Jeff Janes wrote:
>> On Wed, Mar 9, 2016 at 7:02 AM, Tomas Vondra
>> wrote:
>> > Hi,
>> >
>> > thanks for the feedback. Attached is v14 of the pat
nts from the field. Maybe later,
after this has received more field testing.
I won't have a chance to do any further analysis for a while.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
eighted_stddev_samp
--
2887.19919651336
The 5th digit seems too early to be seeing round-off error.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Mar 14, 2016 at 9:27 AM, Artur Zakirov wrote:
> On 14.03.2016 18:48, David Steele wrote:
>>
>> Hi Jeff,
>>
>> On 2/25/16 5:00 PM, Jeff Janes wrote:
>>
>>> But, It doesn't sound like I am going to win that debate. Given that,
>>>
On Wed, Mar 16, 2016 at 8:32 AM, Robert Haas wrote:
>
> Committed with slight changes to the docs, and I added a flag variable
> instead of relying on IdleInTransactionSessionTimeout not changing at
> an inopportune time.
Thanks for committing, this should be a useful feature.
I get a pretty str
(argc=argc@entry=1,
argv=argv@entry=0x26d5a10) at postmaster.c:1208
opt =
status =
userDoption =
listen_addr_saved =
i =
output_config_variable =
__func__ = "PostmasterMain"
#5 0x0047cd1e in main (argc=1, argv=0x26d5a1
holder
receives an error once it tries to access the table again, and then
the bloat stops increasing. But shouldn't the bloat have stopped
increasing as soon as the snapshot became doomed, which would be after
a minute or so?
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hac
On Fri, Mar 18, 2016 at 10:39 PM, Andres Freund wrote:
> Hi,
>
> On 2016-03-18 21:59:01 -0700, Jeff Janes wrote:
>> While testing some patches on my laptop, I noticed my knee getting
>> uncomfortably warm. It turns out I has accumulating deranged logging
>> processes,
On Fri, Mar 18, 2016 at 11:34 PM, David Fetter wrote:
> On Fri, Mar 18, 2016 at 06:12:12PM -0700, Jeff Janes wrote:
>> Also, I think it might not give the correct answer even without
>> negative weights:
>>
>> create table foo as select floor(random()*1)::int
On Sat, Mar 19, 2016 at 11:34 AM, Alvaro Herrera
wrote:
> Jeff Janes wrote:
>> On Sat, Mar 19, 2016 at 8:41 AM, Alvaro Herrera
>> wrote:
>> > I pushed your 25, with some additional minor tweaks. I hope I didn't
>> > break anything; please test.
>>
>
f scripts at all, rather than adding it in a way where it can
never be selected. But then that would complicate the parsing of the
per-script stats report, when one of the scripts was no longer
reported. I like this way better.
Would this be a welcome change?
Cheers,
Jeff
pgbench_zero_wei
t=0.43..1569.70 rows=46812 width=8) (actual rows=6 loops=1)
Index Cond: ((y >= 478) AND (y <= 480))
Heap Fetches: 0
Planning time: 0.175 ms
Execution time: 20.264 ms
(I use the "timing off" option, because without it the second plan
spends most of its ti
"skipped blocks are included this total"
The word "in" is missing
Cheers,
Jeff
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
new file mode 100644
index cb22afb..105d541
*** a/doc/src/sgml/monitoring.sgml
--- b/doc/src/sgml/monitoring.sgml
**
ate, but:
+
+
+ Correctly handle wraparound cases in the pg_subtrans
+ startup logic for hot standby (Jeff Janes)
+
+
This applies to all recovery scenarios, whether they are hot standby
or just plain-old automatic crash recovery. (However, it does only
matter when prepare
On Tue, Jan 12, 2016 at 8:59 AM, Anastasia Lubennikova
wrote:
> 08.01.2016 00:12, David Rowley:
>
> On 7 January 2016 at 06:36, Jeff Janes wrote:
>>
> But now I see the reason to create non-unique index with included columns -
> lack of suitable opclass on column "b&
On Sat, Dec 26, 2015 at 9:12 PM, Jeff Janes wrote:
> On Fri, Dec 18, 2015 at 11:43 AM, Artur Zakirov
> wrote:
>> Hello.
>>
>> PostgreSQL has a contrib module named pg_trgm. It is used to the fuzzy text
>> search. It provides some functions and operators for determ
s a
series of ties).
Finally, should there be operators for returning the distance,
analogous to the <-> operator? It is awkward to use an operator for
the boolean and a function to get the distance. Especially when you
use %> and so need swap the order of arguments between the o
On Sun, Jan 10, 2016 at 4:24 AM, Julien Rouhaud
wrote:
> On 29/12/2015 00:30, Jeff Janes wrote:
>> On Wed, Nov 25, 2015 at 9:29 AM, Jeff Janes wrote:
>>>
>>> I'll prepare a patch for core for the January commitfest, and see if
>>> it flies. If not, ther
he pending list cleanup step when
it finds someone else already cleaning it. For correctness it has to
either clean it itself, or wait until the other process is done (or at
least, done up to the point where the tail was at the time the vacuum
started).
Cheers,
Jeff
--
Sent via pgsql-hackers mail
is current proposal,
and no one has volunteered to do the work on converting it to tuple
sort instead.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
l merge conflicts between your patch and
this commit:
commit 65c5fcd353a859da9e61bfb2b92a99f12937de3b
Author: Tom Lane
Date: Sun Jan 17 19:36:59 2016 -0500
Restructure index access method API to hide most of it at the C level.
Can you rebase past that commit?
Thanks,
Jeff
--
Sent via pgsq
ignal 11, Segmentation fault.
#0 0x00416b0b in dumpAgg (fout=0x1e551e0, agginfo=0x1e65ec0)
at pg_dump.c:12670
12670if (strcmp(aggcombinefn, "-") != 0)
(gdb) bt
#0 0x00416b0b in dumpAgg (fout=0x1e551e0, agginfo=0x1e65ec0)
at pg_dump.c:12670
#1 0x0041df7a in main (argc
es for previous versions.
>
> The attached fixes the problem.
Yep, that fixes it.
Thanks,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
default sorting behavior
LINE 1: alter table foobar add constraint foobar_pkey primary key us...
^
DETAIL: Cannot create a primary key or unique constraint using such an index.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On Wed, Jan 20, 2016 at 6:17 AM, Fujii Masao wrote:
> On Sat, Jan 16, 2016 at 7:42 AM, Julien Rouhaud
> wrote:
>> On 15/01/2016 22:59, Jeff Janes wrote:
>>> On Sun, Jan 10, 2016 at 4:24 AM, Julien Rouhaud
>>> wrote:
>>
>> All looks fine to me, I
itical, as they just
result in getting less specific error messages that one might hope
for, rather than something worse like a panic.
But still, we might want to address them.
Cheers,
Jeff
[1]
http://www.postgresql.org/message-id/CAHGQGwH=m1baejpqdpjjcneqwg8xa+p8sb+zsvhvwh6gl2j...@mail.gmail.com
his is a corner case that probably does not need to be in the docs,
but I wanted to clarify it here in case you disagree: If the index
ever had fastupdate turned on, when it is turned off the index will
keep whatever pending_list it had until something cleans it up one
last time.
Thanks for the review
eaving an active XID hanging around for a few checkpoint cycles,
which is something I've never intentionally tested before.
Cheers,
Jeff
StartupSUB.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
h
ve not updated the extension version. So I
don't know if it makes sense to bump the version if people inherently
get the feature anyway.
Cheers,
Jeff
diff --git a/contrib/pgcrypto/expected/pgp-encrypt.out b/contrib/pgcrypto/expected/pgp-encrypt.out
new file mode 100644
index b35de79..2bf
arning which I think is coming from this commit.
postgres_fdw.c: In function 'fetch_more_data':
postgres_fdw.c:2526:17: warning: unused variable 'fsplan' [-Wunused-variable]
ForeignScan *fsplan = (ForeignScan *) node->ss.ps.plan;
Thanks,
Jeff
--
Sent via pgsql-hackers
02:54:22 2016 +0100
pgbench: improve multi-script support
I wasn't able to figure out which email thread corresponds to this commit.
Thanks,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
On Fri, Feb 12, 2016 at 12:22 PM, Alvaro Herrera
wrote:
> Jeff Janes wrote:
>> If I give pgbench an empty file, I get a segfault.
>>
>> $ touch empty.sql
>> $ src/bin/pgbench/pgbench -T 60 -f empty.sql
>> starting vacuum...end.
>> Segmentation fault (co
On Tue, Feb 9, 2016 at 10:33 AM, Simon Riggs wrote:
> On 9 February 2016 at 18:42, Jeff Janes wrote:
>>
>> While testing the crash resilience of the recent 2-part-commit
>> improvements, I've run into a problem where sometimes after a crash
>> the recovery
On Tue, Feb 16, 2016 at 12:06 AM, Robert Haas wrote:
> On Wed, Feb 10, 2016 at 5:15 PM, Andres Freund wrote:
>> Hi,
>>
>> Several places in our docs have blurbs like
>>> Note that on many systems, the effective resolution of sleep delays is
>>> 10 milliseconds; setting wal_writer_delay to a value
is topic that I'm not aware
of? (The mail archive search interface is not so helpful with common
words like "check".)
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
or could it be added at the
same time as the main patch?
I think this is something it would be pretty frustrating for the user
to be unable to do right from the start.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ttle.
Since the freespace recycling only takes place once the list is
completely cleaned, allowing some processes to add to the end while
one poor process is trying to clean can lead to less effective
recycling.
That is my theory, anyway.
Cheers,
Jeff
--
Sent via pgsql-hacke
there are invisible
un-removable spaces on the substring side.
But, It doesn't sound like I am going to win that debate. Given that,
I don't think we need a different name for the function. I'm fine with
explaining the word-boundary subtlety in the documentation, and
keeping the function name itself simple.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
he planner that could be fixed in a future version,
or is a temp table the only real solution here?
Cheers,
Jeff
there is the requirepeer connection option for that.
>
> Oh, nice, I had not seen that.
>
Hi Bruce,
There is typo in the doc patch you just committed
"On way to prevent spoofing of"
s/On/One/
Cheers,
Jeff
On Thu, Aug 18, 2016 at 2:25 PM, Tom Lane wrote:
> Jeff Janes writes:
> > So even though it knows that 6952 values have been shoved in the bottom,
> it
> > thinks only 200 are going to come out of the aggregation. This seems
> like
> > a really lousy estimate. In mo
0x003838ce1503 in __select_nocancel () at
../sysdeps/unix/syscall-template.S:82
#20 0x006b0ec0 in ServerLoop (argc=,
argv=) at postmaster.c:1657
#21 PostmasterMain (argc=, argv=)
at postmaster.c:1301
#22 0x00632e88 in main (argc=4, argv=0x11f4d50) at main.c:228
Cheers,
Jeff
_pg_index rd_index;
^
commit ed0097e4f9e6b1227935e01fa67f12a238b66064
Author: Tom Lane
Date: Sat Aug 13 18:31:14 2016 -0400
Add SQL-accessible functions for inspecting index AM properties.
I don't know if this compiler is a too clever by half, or not clever enough.
Cheers,
Jeff
--
On Tue, Aug 23, 2016 at 10:05 PM, Amit Kapila
wrote:
> On Wed, Aug 24, 2016 at 2:37 AM, Jeff Janes wrote:
>
> >
> > After an intentionally created crash, I get an Assert triggering:
> >
> > TRAP: FailedAssertion("!(((freep)[(bitmapbit)/32] &
> >
On Mon, Aug 22, 2016 at 10:19 AM, Robert Haas wrote:
> On Sat, Aug 20, 2016 at 4:58 PM, Tom Lane wrote:
> > Jeff Janes writes:
> >> On Thu, Aug 18, 2016 at 2:25 PM, Tom Lane wrote:
> >>> It does know it, what it doesn't know is how many duplicates there are
On Tue, Aug 9, 2016 at 5:17 PM, Jim Nasby wrote:
> On 8/5/16 12:00 PM, Jeff Janes wrote:
>
>> So I created a new guc, notice_lock_waits, which acts like
>> log_lock_waits but sends the message as NOTICE so it will show up on
>> interactive connections like psql.
>&g
store the list of FPI pages. For the second one, you
would not want it to run so far ahead that it the pages it read in would
get pushed out again before the lagging process got to them. Controlling
how far ahead that would be seems like it would be hard.
Cheers,
Jeff
ckets with at least one overflow page, and split when
there are too many of those. I bring it up now because it would be a shame
to ignore it until 10.0 is out the door, and then need to break things in
11.0.
Cheers,
Jeff
ble-casserts, to I will have to
redo it to make sure the assertion failures have been fixed. In my
original testing I did very rarely get a deadlock (or some kind of hang),
and I haven't seen that again so far. It was probably the same source as
the one Mark observed, and so the same fix.
Cheers,
Jeff
iodically interrupt the process (ctrl c) and take
a back trace (bt), then restart it (c) and repeat. If all the stack traces
look similar, you will know where the time is going.
Cheers,
Jeff
any of multiples of
each of the *_cost factors were summed to arrive at the total cost. that
would help me a lot in interpreting plans, and might also help someone like
Depesz a lot in improving his expert-system.
It would be far easier than what you are proposing, but would be still be a
lot of work. It would probably also be challenged because the accounting
overhead, while small, would be incurred on every single planner run.
Cheers,
Jeff
On Thu, Sep 8, 2016 at 12:09 PM, Jeff Janes wrote:
> I plan to do testing using my own testing harness after changing it to
> insert a lot of dummy tuples (ones with negative values in the pseudo-pk
> column, which are never queried by the core part of the harness) and
> deleting th
On Sun, Sep 11, 2016 at 7:40 PM, Amit Kapila
wrote:
> On Mon, Sep 12, 2016 at 7:00 AM, Jeff Janes wrote:
> > On Thu, Sep 8, 2016 at 12:09 PM, Jeff Janes
> wrote:
> >
> >>
> >> I plan to do testing using my own testing harness after changing it to
> >
On Wed, Sep 7, 2016 at 9:32 PM, Amit Kapila wrote:
> On Wed, Sep 7, 2016 at 11:49 PM, Jeff Janes wrote:
> > On Thu, Sep 1, 2016 at 8:55 PM, Amit Kapila
> wrote:
> >>
> >>
> >> I have fixed all other issues you have raised. Updated patch is
> &g
(flags) */
+ if (opaque->hasho_flag & LH_UNUSED_PAGE)
+ stat->type = 'u';
This can never be true, because LH_UNUSED_PAGE is zero. You should make
this be the fall-through case, and have LH_META_PAGE be explicitly tested
for.
Cheers,
Jeff
On Tue, Sep 13, 2016 at 9:31 AM, Jeff Janes wrote:
> ===
>
> +Vacuum acquires cleanup lock on bucket to remove the dead tuples and or
> tuples
> +that are moved due to split. The need for cleanup lock to remove dead
> tuples
> +is to ensure that scans' returns c
vement in read only)
I've run this was 128MB shared_buffers and scale factor 40. Not everything
fits in shared_buffers, but quite easily fits in RAM, and there is no
meaningful IO caused by the benchmark.
Cheers,
Jeff
unhappy to try to compare WAL
logged concurrent hash indexes to btree-over-hash indexes, if I had to wait
a few years for the latter to appear, and then dig up the patches for the
former and clean up the bitrot, and juggle multiple patch sets, in order to
have something to compare.
Cheers,
Jeff
ly care about the algorithm for inserting in
isolation, I agree reading the code might be better.
But the use of white space isn't always consistent, and I don't know what a
double hyphen means. I think it could use improvement, rather than
abolishing.
Cheers,
Jeff
ve doubt and
> they want to test some specific cases, then sure we can do more
> performance benchmarking.
>
I think that a precursor to WAL is enough to justify it even if the
verified performance improvements were not impressive. But they are pretty
impressive, at least for some situations.
Cheers,
Jeff
1 - 100 of 3210 matches
Mail list logo
