GUC as suggested. What's your take on the
attached patch?
-sc
--
Sean Chittenden
se...@joyent.com
On Oct 4, 2017, 10:56 AM -0700, Andres Freund <and...@anarazel.de>, wrote:
> Hi,
>
> On 2017-10-04 10:47:06 -0700, Sean Chittenden wrote:
> > Hello. We identified the same
if there are any questions. -sc
--
Sean Chittenden
se...@joyent.com
if there are any questions. -sc
--
Sean Chittenden
se...@joyent.com
ism.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
:12.307880900 +0300
@@ -3,3 +3,4 @@
case $host_cpu in
alpha*) CFLAGS=-O;; # alpha has problems with -O2
esac
+USE_NAMED_POSIX_SEMAPHORES=1
-sc
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
=mmapapropos=0sektion=0manpath=FreeBSD+10.0-stablearch=defaultformat=html
[3]
http://www.freebsd.org/cgi/man.cgi?query=madvisesektion=2apropos=0manpath=FreeBSD+10.0-stable
--
Sean Chittenden
diff --git a/src/backend/storage/ipc/dsm_impl.c
b/src/backend/storage/ipc/dsm_impl.c
index 0819641..1c3aa9a
).
I made a cursory pass over the code and found one other instance where write
status wasn’t being checked and also included that.
-sc
pg_dump_check_write.patch
Description: Binary data
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers
so I thought
I’d prod and ask. Thanks in advance. -sc
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
on /dev/random on some systems and that's
the source of unreliability/timeouts.
[1] commit 17386ac45345fe38a10caec9d6e63afa3ce31bb9
Author: Bruce Momjian br...@momjian.us
Date: Wed Jun 11 15:05:50 2003 +
patch by Sean Chittenden (in CC), posted as [2]
[2]
http
[1] http://botan.randombit.net/tls.html?highlight=renegotiate
--
Sean Chittenden
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
was. Attached is an improved error message:
ERROR: XX000: no schemas in search_path are available for CREATE EXTENSION
-sc
src-backend-commands-extension.c.patch
Description: Binary data
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
or empty
the directory /tmp/pginit-test or run initdb
with an argument other than /tmp/pginit-test.
[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/174020
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
that aren't dot directories so this seems like a relatively
futureproof solution, too.
lost+found
It's been a long time since I've seen that directory. Patch updated. -sc
--
Sean Chittenden
s...@chittenden.org
src-port-pgcheckdir.c.patch
Description: Binary data
--
Sent via pgsql-hackers
that I'm sure is covered someplace in
the handbook. A general warning isn't a bad idea, however. *shrug*
Regardless, hopefully some of this is of interest to someone.
-sc
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
methodology. Using INT8 internally was too
convenient at the time.
--
Sean Chittenden
s...@chittenden.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
storage/lmgr/proc.c for the
LISTEN/NOTIFY interface? It looks like SIGALRM has a reserved purpose.
I haven't found any global alarm handling interface that can be used
to assign different meanings when an SIGALRM is received. Any other
thoughts on the best way to proceed?
-sc
--
Sean
to work and will revisit extending things further once I have this bit
done. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
is that this doesn't work in pl/*, which is the problem I
was trying to address. *shrug* -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
too, fwiw. I don't have any 7.X boxen around though,
they're all on 8.X now. :) I'm very interested in feedback. Anyway,
please let me know if anyone has any questions or problems. I'm
holding off on posting to announce@ for another week or so, maybe after
the 8.0 release. -sc
--
Sean
://people.FreeBSD.org/~seanc/pgmemcache/pgmemcache.pdf
Fixed. Thanks for pointing that out.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
if you haven't yet. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
TRIGGER tbl_inval_trg AFTER INSERT OR UPDATE OR DELETE ON
schma.tbl FOR EACH STATEMENT EXECUTE PROCEDURE schma.tbl_inval();
Very nice. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http
it more.
I'm confused... UDP as in the UDP/IP? RPC caps UDP messages at 8K and
NFS over UDP often runs at 32K... where is UDP used in the backend?
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 6: Have you searched our list archives
thumb.
Would you be open to increasing this further after the 8.0 release? I
haven't heard of anyone complaining about dropped/fragmented pgstat
messages. :) -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
programs
and its libs. I'm sure other packagers may wish to see this happen
too. *shrug* -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
on here and will submit a fix for this sometime
tonight. -sc
I think Tom applied a patch already for this.
:) So I noticed. I went to update my sources before sending off a
patch and was greeted with a rather nice conflict. Thanks for getting
to that Tom. -sc
--
Sean Chittenden
on here and will submit a fix for this sometime
tonight. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 8: explain analyze is your friend
the existence of directories as
well as the permissions?
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
SET search_path and have that work without
checking.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message
of the olden days when
/etc/passwd contained crypt(3)'ed passwords and home directories were
created mod 755 or umasks were 0 by default and a mask of 022 was a
umask for the overly paranoid.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1
the database and type df
-k sync sleep 30 df -k see space being freed up. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Sean Chittenden
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
operates on
pg_catalog_cluster.
Tom, what do you think? What other ideas do you have kicking around in
your head?
*shrug* Something for the TODO list and/or an inspired hacker. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 9: the planner
.
Nope, other way round, default behavior for backwards compatibility
must
be to create cluster-wide users. CREATE LOCAL USER is what to add.
Ah, good point. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 2: you can get off all lists at once
the password for a local user by the
same name.
Agreed, but if a cluster is using LOCAL USERs, I doubt highly that
CLUSTER/GLOBAL users would be in use much beyond super users. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 3: if posting/reading through
.
And it doesn't handle the case of letting the local database admin
create users (without giving them access to the rest of the database),
which is what I'm after. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 8: explain analyze is your friend
to a majority and just lead to upgrade thrashing which
is costly to organizations. Food for thought... nothing conclusive
here. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 8: explain analyze is your friend
-patches/2003-07/msg00053.php
pg_ping is actually the basis for the threaded benchmark program I've
got sitting in my tree, but I don't think folks here would look kindly
on a -lpthread dependency given how up in the air pg's thread
support/testing is at the moment. -sc
--
Sean Chittenden
to hear
from the GCC folks.
Well, I have no insite into the gcc camp, but, my understanding is
that gcc 3.3 for the alpha isn't broken, but for gcc 2.X, it's pretty
horked with any level of optimization. -sc
--
Sean Chittenden
---(end of broadcast
, it's likely that many folks won't notice any appreciable
difference (though it does add up). Here's a thread worth reading
from the gcc guys:
http://gcc.gnu.org/ml/gcc-bugs/2000-10/msg00138.html
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 9
warehouse
operations, 32K pages would be the way to go, esp when it comes
time to run reports. With 8K pages, I couldn't max out the IO, but
with 32K, it's very possible and much easier to do. Beyond that, I
don't have much else I want to comment on at the moment.
-sc
--
Sean
, or alternative quoting, maybe.
Those seem pretty unmemorable and content-free, though. Any other ideas
out there?
literal text blocks
literal quotes
literal text sections
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 4: Don't 'kill -9
.{
/* Not sure these func names off the top of my head: */
pg_append_str_to_buf(lit_val, yytext, yyleng);
}
%%
/* Or something similarly flexible */
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe
) operator names in
Postgres, so we could not use them for this purpose without removing
that meaning, which would be painful.
Really? Hrm, guess @'s out. $ works for me.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 2: you can get off all
to be linked with ncurses (288K)
and readline (156K)? It's .5M, not the end of the world, but it seems
excessive. I know the postmaster has a CLI interface, but does it
really require ncurses or readline? -sc
--
Sean Chittenden
---(end of broadcast
such). It's chump, but a few ms
here and there, or a little more IO there eventually add up,
especially in the arena of on connection times.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
the comment in backend/storage/ipc/ipci.c is out of date then:
* AttachSharedMemoryAndSemaphores
* Attaches to the existing shared resources when exec()'d off
* by the postmaster.
-sc
--
Sean Chittenden
---(end of broadcast
Does anybody know of a BSD licensed signal implementation that
compiles on win32?
See how Apache handles this problem (via APR?).
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
'nother test in support of 16K blocks for FreeBSD, this time it was
25% faster to import. -sc
--
Sean Chittenden
---BeginMessage---
Hi.
I'm implementing postgresql 7.3.4 on FreeBSD 5.1, and
decided to place the pgsql-folder on it's own
partition so it was easier to test which blocksize to
go
going to task with comparing 16K
and 8K blocks. It's not SCSI, but I don't have any available machines
that I can newfs + reinstall PostgreSQL on. I was thinking about
running the regression tests 10x ...
-sc
--
Sean Chittenden
---(end of broadcast
be interested
in those results to see if it's still 8% faster. In using 16K blocks,
I'd imagine this'll make using seq scans cheaper on FreeBSD.
Comments? -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 3: if posting/reading through Usenet
the port gets built, so there doesn't need
to be a configuration option for it for this to work.
--
Sean Chittenden
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
still 8% faster.. I imagine this'd
make seq scans cheaper on FreeBSD.
Comments? -sc
--
Sean Chittenden
---BeginMessage---
Like all benchmarks, I doubt these are perfect (or even close)
examples of real-world use.
However, in the hopes that they will be useful for improving FreeBSD, I
of uncovering bugs
because this hasn't been widely done like this before, do you have any
other concerns, or do you think the possibility of finding bugs very
likely?
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
in the 7.4 release notes
and remove support for it for 7.5, giving users one full release cycle
to move to krb5.
There any plans to include the appropriate verbiage to allow for krb4's
future deorbit?
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 6
as almost everyone who uses krb
uses hiemdal or MIT krb5. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
..85.75 rows=514 loops=1)
Index Cond: (html_bytes 800::bigint)
Total runtime: 97.75 msec
(3 rows)
*shrug* A low indexCorrelation overly pessimizes the cost of an index,
but I'm not sure where to attribute this too. :-/
-sc
--
Sean Chittenden
---(end
to the prepared statement.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
and I
thought was very clever, albeit space intensive. *shrug*
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
;
And various timestamps back to 2002-09-19 and user_id's IN(1,42).
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
access to if they'd like. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
know you just replaced a bunch of select() calls with poll().
Would you mind if I went through and patched things to use libevent's
abstraction layer?
Once this is done, then I'll go back and use libevent for the
persistent connections goo. -sc
--
Sean Chittenden
---(end
/* LONGLONG */
typedef long long __int64_t;
/* LONGLONG */
typedef unsigned long long __uint64_t;
#endif
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 8: explain analyze is your friend
be nice for big queries that
have lots of smaller queries running around at the same time.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
documentation about it. Especially the krb_sendauth() function.
Does Kerberos 4 support other protocols than ipv4?
Not that I'm aware of. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
has an idea of how much data it's going to read in in order to
complete the query, seems easier/better to mark the fd O_DIRECT.
*shrug*
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http
a threaded app and doesn't use
non-blocking IO. The backend would block until the call returns,
where's the problem? :)
If anything O_DIRECT would shake out any bugs in PostgreSQL's caching
code, if there are any. -sc
--
Sean Chittenden
---(end of broadcast
restriction.
I don't see how this'd be an issue as buffers populated via a read(),
that are updated, and then written out, would occupy a new chunk of
disk to satisfy MVCC. Why would we need to mark a buffer as read only
and carry around/check its state?
-sc
--
Sean Chittenden
system performance when a
query is using O_DIRECT or are you looking for negative/postitve
impact of read() not using the FS cache? The latter is much easier to
do than the former... recreating a valid load environment that'd let
any O_DIRECT benchmark be useful isn't trivial.
-sc
--
Sean Chittenden
as is).
http://lists.freebsd.org/pipermail/cvs-all/2003-March/000261.html
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
in RAM.
--
Sean Chittenden
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
() writes into that way the
HDD could just DMA the data into the mmap()'ed buffer making it a
zero-copy read operation though stirring any interest with my
mmap() benchmarks from a while back seems to me have been lost in the
fray. :)
-sc
--
Sean Chittenden
---(end
to be in
the userland and would require the use of O_DIRECT.
Actually, I think of O_DIRECT as platform-dependent.
FreeBSD, IRIX, and AIX, implement it, and ... *smiles with pride*
looks like Linux does too given the number of security vulnerabilities
associated with the call. :-]
-sc
--
Sean
PostgreSQL leaves all of the caching
operations and optimization/alignment of pages up to the OS (much to
the behest of madvise() which could potentially speed up access of the
VM, but I won't get into that... see TODO.mmap).
-sc
--
Sean Chittenden
---(end of broadcast
of FreeBSD?
-sc
--
Sean Chittenden
pgp0.pgp
Description: PGP signature
*
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
of detecting this, does the
following work?
if [ `uname` = FreeBSD ]; then
if [ `sysctl -n kern.osreldate` -ge 500110 ]; then
echo Has new gdtoa: new float handling
else
echo Older float routines
fi
fi
-sc
--
Sean Chittenden
fixes the regression tests on my
5.1... I don't have any 4.X machines I can play with at the moment,
Rod would have to test that.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
of float overflow
and underflow conditions, which PostgreSQL used to work around Now
that 5.1 is fixed with respect to float handling, the regression tests
were b0rk3d. The above fixes things so that PostgreSQL works in both
the 4.X and 5.X cases even though their handling is different. -sc
--
Sean
preserving
backward compatibility, you could add freebsd2 and freebsd3 to the
list too.
-sc
--
Sean Chittenden
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
, the
documentation and release notes need to state that krb4 has been
depreciated and that it will be removed before 7.5. I'll add submit a
patch for the updated verbiage in a bit. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
. Historically, PostgresSQL has been consistently
^^ ^^^
ahead of MySQL in enterprise database features with support of
transactions and stored procedures.
heh, understatement of the year++ for an understated project.
-sc
--
Sean Chittenden
---(end of broadcast
. -sc
--
Sean Chittenden
pgp0.pgp
Description: PGP signature
database
to do something truly useful with XQuery concepts.
Um, why change the backend at all? Why not have libpq do the
interference mapping between the front end and backend so that we can
leave the backend alone? Seems like a simple application of a good
SAX parser to me. -sc
--
Sean
do
this in a few weeks if someone doesn't beat me to it.
--
Sean Chittenden
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
, but since it is actively being developed by
resources outside of this project, and it has support for 16-bit and
32-bit encodings (UCS-2, UCS-4, UTF-16) is on the TODO list, it might
be nice to keep this in mind and let Ruby maintain it instead of
PostgreSQL.
-sc
--
Sean Chittenden
? -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
having transaction
B re-run its queries.
Like I said, it ain't perfect, but what would be a better solution?
::shrug:: Even OODB's with stats agents have this problem (though
their overhead for doing this kind of work is much much lower). -sc
--
Sean Chittenden
---(end
auto_collapse_join
auto_collapse_num_join
auto_join_threshold
When I'm thinking about what this variable will do for me as a DBA, I
think it will make the plan more intelligent by reordering the joins.
My $0.02. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP
for it through the nose. -sc
--
Sean Chittenden
msg27765/pgp0.pgp
Description: PGP signature
do a make distclean.
FreeBSD 4.7
I'm still not able to duplicate any problem. Any other FreeBSD folk see
inet regression failures in CVS tip?
Unable to reproduce this on 5.0 with PostgreSQL HEAD as of 8:10PST.
-sc
--
Sean Chittenden
---(end of broadcast
the new standard
port people won't be bitten so much by the library version bump.
The -devel port has been out for a few months, those that are serious
DBAs likely have a staging/test environment to work with. If anyone
runs across any serious problems on FreeBSD, let me know ASAP.
-sc
--
Sean
=geometry-bsd-precision
geometry/i.86-.*-freebsd5=geometry-bsd-precision
geometry/alpha.*-freebsd=geometry-positive-zeros
Sean, would you verify this works for you?
It does, thank you. I've just updated the -devel port to 7.3b4,
hopefully the mirrors will pick up the bits soon. -sc
--
Sean
),(-0.301775147928994,0.0414201183431953)
|
(-0.251479289940828,0.103550295857988),(-0.322485207100592,0.0739644970414201)
|
(-0.301775147928994,0.124260355029586),(-0.301775147928994,0.124260355029586)
==
--
Sean
to move. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
not in a transaction, but now that there are some intricate rules
with regards to starting transactions, I'd love to provide a DBI
interface into a call that returns whether or not we're in a
transaction to prevent millions of these:
NOTICE: ROLLBACK: no transaction in progress
-sc
--
Sean
that in application is getting pretty
gnarly. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
will be employed instead?
Anyone thought about using GeoIP and writing a script that'd dump the
database into something that could be postgresql usable? Just a
thought. -sc
--
Sean Chittenden
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
. 'nother few
weeks before beta2 or is it right around the corner?
For those interested in PostgreSQL + FreeBSD, I have a patch pending
approval that will let developers toggle between a devel port and the
stable release for all ports that depend on PostgreSQL.
-sc
--
Sean Chittenden
1 - 100 of 121 matches
Mail list logo
