about.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
the chance that a page
will be kept in buffer cache after it's been used.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Andrew Sullivan [EMAIL PROTECTED] writes:
On Sun, Nov 02, 2003 at 01:00:35PM -0500, Tom Lane wrote:
real traction we'd have to go back to the take over most of RAM for
shared buffers approach, which we already know to have a bunch of
severe disadvantages.
I know there are severe
Neil Conway [EMAIL PROTECTED] writes:
On Mon, 2003-11-03 at 10:01, Tom Lane wrote:
I would expect POSIX_FADV_SEQUENTIAL to reduce the chance that a page
will be kept in buffer cache after it's been used.
I don't think that can be reasonably implied from the POSIX text, which
is merely
[EMAIL PROTECTED] writes:
I'm a bit unfamiliar with this stuff, so I wanted to ask if this was
something that Linux appears to be handling differently than other OS's,
or if this was a platform specific issue with postgresql.
It's generic to all Unixen.
regards, tom
Neil Conway [EMAIL PROTECTED] writes:
On Mon, 2003-11-03 at 11:11, Tom Lane wrote:
Why not? The advice says that you're going to access the data
sequentially in the forward direction. If you're not going to back up,
there is no point in keeping pages in cache after they've been read
Marc G. Fournier [EMAIL PROTECTED] writes:
On Tue, 4 Nov 2003, Gaetano Mendola wrote:
Is in the last Tom's patch about Vacuum sleep between pages ?
that won't be in v7.4, to the best of my knowledge ...
Definitely not. It's a very experimental patch.
regards, tom
preferred not to break compatibility with Tcl 8.0.*, but I
didn't see a whole lot of alternatives. There isn't any other way
AFAICS to prevent recent Tcl releases from applying an unwanted
translation.
regards, tom lane
---(end of broadcast
at which writes are issued,
and there's no I/O storm at all. (fsync could still cause an I/O storm
if there's lots of pending writes in a single file.)
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
I have never been happy with the fact that we use sync(2) at all.
Sure does it do too much. But together with the other layer of
indirection, the virtual file descriptor pool, what is the exact
guaranteed behaviour of
write(); close
. This has been discussed before, see the archives:
http://archives.postgresql.org/pgsql-hackers/2002-11/msg00488.php
http://archives.postgresql.org/pgsql-hackers/2002-11/msg00679.php
http://archives.postgresql.org/pgsql-hackers/2002-11/msg00512.php
regards, tom lane
flushing metadata that much?
We don't, but it would just obscure the discussion to spell out fsync,
or fdatasync where available ...
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
happening. (I doubt that it does, anyway. I think the issues are
probably quite localized. The main problem I see is that we don't have
any trustworthy check to find out everyplace that strict aliasing could
cause problems.)
regards, tom lane
---(end
a roundoff issue,
and as such a legitimate platform-specific behavior.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
that MSG_NOSIGNAL
should be used when available in their standard release, or at least
they should provide an option to use it? The alternative would be to
create our own BIO for libssl, which I think is doable, but would likely
be a pain in the neck to maintain.
regards, tom
include in the server distribution. I think it
would be great to put it up on gborg.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Greg Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
The main problem with this is knowing which files need to be fsync'd.
Why could the postmaster not just fsync *every* file?
You want to find, open, and fsync() every file in the database cluster
for every checkpoint
not convinced once per outer loop is a sufficient answer.
Otherwise this is sounding pretty good.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs
. I think Peter E. is looking into what it would take to
fix this for 7.5, but at present you are going to need to use a
single-byte encoding within the server. (Nothing to stop you from using
UTF-8 on the client side though.)
regards, tom lane
[EMAIL PROTECTED] writes:
After spending a few hours of trying to get Postgresql7.3.4 to build
from source (tar.gz) on a Panther (release, not beta) system,
Try 7.4RC1 instead. Apple made some incompatible changes in their
compiler in Panther.
regards, tom lane
excessively dependent on the assumption that the character
set is ASCII. Why have you hard-coded numeric equivalents into this
macro?
BTW, the patch is incomplete because it is lacking documentation.
regards, tom lane
---(end of broadcast
on
multi-CPU systems.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
is concerned?
How would that tell you about currently outstanding operations?
Manfred's idea is interesting but AFAICS completely unimplementable
in any portable fashion. You'd have to have hooks into the kernel.
regards, tom lane
---(end
original VACUUM-delay
hack (or even a production-grade version of same, which'd probably be
10x larger). The kind of wholesale rewrite you are currently proposing
is much too large to consider folding back into 7.4.*, IMHO.
regards, tom lane
children of a master table. Then selecting from the master
would work (and would be equivalent to the UNION performance-wise, I
think).
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ
no one tries to
run Postgres on any EBCDIC platform. (It's likely that there are other
places that depend on the letters-are-contiguous assumption anyway.)
I do think level 1 and probably level 2 are appropriate changes.
regards, tom lane
---(end
the tables that you
could reference with unqualified names. Which does not include the
tables in test_002, because they're hidden by the ones in test_001.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore
such. Please make sure that Tom Lockhart and Vadim
get listed that way, at least.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
of pointing
out that we have a worldwide development community. We can just say
that...
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
, and no way for
7.4, but we can look at it later for the S_UNLOCK change.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do
/pgsql-hackers/2003-10/msg01521.php
and so far as I saw no one responded one way or the other.
* PPC spinlock patch from SuSE.
See my prior response.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all
, where it wouldn't. If you're unsure that you
affected it, check out the actual sizes of the array values in pg_stats.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send
...
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
?
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
constraint without obtaining some kind of schema-wide lock.
See prior discussions.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
(or after) the $1.
I don't have a problem with switching from $1 to tablename_$1, or
some such, for auto-generated constraint names. But if it's not
guaranteed unique, does it really satisfy Philip's concern?
regards, tom lane
---(end of broadcast
Alvaro Herrera [EMAIL PROTECTED] writes:
On Thu, Nov 06, 2003 at 11:42:13AM -0500, Tom Lane wrote:
I don't have a problem with switching from $1 to tablename_$1, or
some such, for auto-generated constraint names. But if it's not
guaranteed unique, does it really satisfy Philip's concern
of trying to bind to both IPv6 and IPv4 sockets would be
unnecessary if the kernels acted more rationally.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
is
sponsoring a developer. Seems to me that's a bit narrow-minded.
For instance, hub.org is contributing (by providing hosting services)
way more than you might think from the number of times it appears on
the developer list...
regards, tom lane
---(end
. Can you step through StreamServerPort,
or perhaps just strace postmaster startup, to observe the sequence of
bind() calls? It would be useful to know which addresses have already
been bound and which one is failing.
regards, tom lane
---(end
():
/*
* Note: This might fail on some OS's, like Linux older than
* 2.4.21-pre3, that don't have the IPV6_V6ONLY socket option, and
* map ipv4 addresses to ipv6.It will show :::ipv4 for all
* ipv4 connections.
*/
regards, tom lane
appear in a default setup;
but I'm not sure I'm for that either.
Given the, ahem, wide variety of behaviors that seem to be out there,
I think we'd best be happy if we have a v4/v6 implementation that has
no problems worse than spurious log messages ...
regards, tom lane
it to the 7.3 branch as well.
regards, tom lane
*** src/backend/port/sysv_shmem.c.orig Mon Oct 27 13:58:00 2003
--- src/backend/port/sysv_shmem.c Thu Nov 6 18:10:02 2003
***
*** 253,258
--- 253,261
return hdr
the table name to the view does have
some merit though.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
how additional people could get involved.
Or do you *want* to keep the web group too small to get things done?
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
is a bit of a PITA).
regards, tom lane
---(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
, IPPROTO_TCP, TCP_NODELAY,
(char *) on, sizeof(on)) 0)
{
elog(LOG, setsockopt(TCP_NODELAY) failed: %m);
return STATUS_ERROR;
}
#endif
Better ask them what their problem is with that ...
regards, tom lane
). To do anything like the above,
you'd need to find different solutions to these problems.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
regression=# create table foo (f1 int check (f1 0) check (f1 10));
ERROR: check constraint foo_f1 already exists
Is this a TODO to fix?
Probably should be. I'd be inclined to try to fix it by generating
foo_f1_1, foo_f1_2, etc until
would improve matters.
Otherwise I think this is probably an HPUX bug. You might need to get a
more recent version of libc.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
Andriy Tkachuk [EMAIL PROTECTED] writes:
Nov 5 20:22:42 monstr postgres[16071]: [3] PANIC: open of
/usr/local/pgsql/data/pg_clog/0040 failed: No such file or directory
Could we see ls -l /usr/local/pgsql/data/pg_clog/
regards, tom lane
opaque IMNSHO.
Agreed. I think using the OIDs would be a horrible choice.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
, but
I'd still be happier if we could eliminate the risk rather than just
reduce it.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
ms every N blocks, instead of N ms every
block) but it did seem that there was useful bang for little buck there.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
a hard code freeze in place then, with only docs changes allowed
before the release is wrapped next Sunday.
[ core guys: that is what we agreed to, right? ]
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading
their underlying catalog data changes
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
duplicate reports and doing the right cleanup, etc. Do we have any
volunteers for that sort of thing?
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Jan Wieck [EMAIL PROTECTED] writes:
Tom Lane wrote:
The attached patch fixes the problem by causing the stats collector to
detach from shared memory, which it isn't using anyway.
I seem to recall there once was a pipe from the postmaster to the stat's
processes and closing
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
.
The doesn't quite make the best use of PG quote is one of the best
examples of buck-passing I've seen in awhile. If Bugzilla had been
designed with some thought to DB independence to start with, we'd not
be having this discussion.
regards, tom lane
.
* I ditched the system.c hack, assuming Apple has fixed them by 10.3 --
because it breaks tcl and python if you do.
I don't see why system.c would affect the problem I'm seeing --- does
this really fix pltcl for you?
regards, tom lane
---(end
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
I have just in the past couple hours realized that ps_status.c is
seriously broken on OS X 10.3. It appears that Apple has randomly
decided to start #define'ing BSD,
__APPLE__ is usually the only define you
.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
solution of letting the planner try to commute the clause to put
the indexkey on the left seems to work fine.
I'm planning to push forward with trying to implement this. Any comments,
ideas, objections?
regards, tom lane
---(end of broadcast
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
One way in which we will lose some flexibility is that this design nails
down forevermore the assumption that the indexed column is on the lefthand
side of any indexable clause.
I don't see this as a problem, but if it becomes one
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 12:31 AM, Tom Lane wrote:
I have just in the past couple hours realized that ps_status.c is
seriously broken on OS X 10.3.
Er... I meant memcmp.. Have you tried removing the system.c hack?
That's what fixed it for me.
AFAICT
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 8, 2003, at 1:13 PM, Tom Lane wrote:
As for getting rid of system.c, I am not eager to do that since it
would
certainly break compatibility with OS X 10.1. We could conditionally
compile it out perhaps. Do you know what #define symbol we could
/Makefile.global to have
python_libspec = -framework Python
I'm not going to touch that at this point in the release cycle. It'll
just have to wait for a future release.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't
true in
certain object-file formats.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
then you can see it in EXPLAIN
output. Functions in the SELECT list you can't see without wading
through EXPLAIN VERBOSE (or equivalently debug_print_plan).
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading
the Value node into a numeric OID, ie, either do intVal() or
a call of oidin().
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Greg Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
You want to find, open, and fsync() every file in the database cluster
for every checkpoint? Sounds like a non-starter to me.
Except a) this is outside any critical path, and b) only done every few
minutes and c
.
Good catch. There are two other places with the same typo :-( (all
copied and pasted no doubt).
I've applied the patch but am loathe to force an initdb this late in
the beta cycle. Any opinions out there?
regards, tom lane
---(end of broadcast
Marc G. Fournier [EMAIL PROTECTED] writes:
On Sat, 8 Nov 2003, Tom Lane wrote:
I've applied the patch but am loathe to force an initdb this late in
the beta cycle. Any opinions out there?
Annoying as a spelling mistake is (and, from my read of the above, that is
all it is?), I don't thnk
want to
re-initdb.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
on a pg_simple_upgrade
procedure.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
with following the lead of the existing code?
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Andriy Tkachuk [EMAIL PROTECTED] writes:
On Fri, 7 Nov 2003, Tom Lane wrote:
Andriy Tkachuk [EMAIL PROTECTED] writes:
Nov 5 20:22:42 monstr postgres[16071]: [3] PANIC: open of
/usr/local/pgsql/data/pg_clog/0040 failed: No such file or directory
Could we see ls -l /usr/local/pgsql/data
.)
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
, which seems rather a large loss.
Also, if cache_head ever becomes non-null then it stops trusting its
internal knowledge as well, which seems worse.
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase
multiple writer processes, which I believe is Oracle's
solution.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
burrow down through any RelabelTypes
for any/anyarray/anyelement.
Comments?
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
Joe Conway [EMAIL PROTECTED] writes:
Tom Lane wrote:
Joe, do you recall the reasoning for this code in parse_coerce.c?
[much snipped]
Does the RelabelType keep a record of what was relabeled (I presume from
your description above it does)?
The RelabelType node itself doesn't, but you can
Michael will be wanting to look for another solution anyway...
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
.)
regards, tom lane
---(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
...
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane writes:
Actually, I think that that may be expected behavior depending on the
vintage of the kernel. Note the following comment in
StreamServerPort():
Can we make the warning less misleading if IPV6_V6ONLY does not exist?
Possibly. How
Kiyoshi Sawada [EMAIL PROTECTED] writes:
On Tue, 11 Nov 2003 09:18:48 -0500 Tom Lane [EMAIL PROTECTED] wrote:
So why not? Try looking in the postmaster log for errors related to
stats collector startup. (pstat is irrelevant, btw.)
LOG: could not bind socket for statistics collector
the
effective support is none at all, and people have got to hold their
feet to the fire about it.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
routines'
fault. But AFAICT Kiyoshi's problem is not that ... unless maybe
localhost is incorrectly listed as something other than 127.0.0.1
in one of those sources?
regards, tom lane
---(end of broadcast)---
TIP 8: explain
the error messages more verbose, or added a debug-level
message to show what addresses are being tried.
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
about that, or other ideas
altogether?
For the moment I'm satisfied with what we have; this is already a big
step forward on a problem that's been there forever. But there's always
something else that could be done ...
regards, tom lane
---(end
Jan Wieck [EMAIL PROTECTED] writes:
I have just committed the implementation of ARC into the 7.5devel tree.
I'm seeing a whole bunch of regression test failures that weren't there
half an hour ago ...
regards, tom lane
---(end of broadcast
at least to me).
But on my HP machine all that stuff seems to play nice. On my Linux
machine, which I cvs updated just a little bit later, problems :-(
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe
else involved.
regards, tom lane
*** ./expected/name.out Sun May 25 20:11:28 2003
--- ./results/name.out Wed Nov 12 22:16:27 2003
***
*** 90,126
(6 rows)
SELECT '' AS seven, c.f1 FROM NAME_TBL c WHERE c.f1 ~ '.*';
! seven
,
but regression tests fail hard. diff -r confirms that the only
difference in the source trees is your ARC patch. Configuration in
both cases is --enable-cassert --enable-debug ...
regards, tom lane
---(end of broadcast
() in the trace.)
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
not?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
on Solaris; but it is not yet clear
whether that's our bug or a misconfiguration problem on those boxes,
and I don't want to hold up the release while we find out.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill
1 - 100 of 46745 matches
Mail list logo
