.
I thought that was a good argument actually.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
the three hashes
together which reduces it to the solved problem.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
, digits, underscore?
Or does it need to be weaker than that?
What's the problem with .?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
could be in
it by default. But that might depend on how expensive it is at run-time. I
wouldn't want trivial SQL functions to no longer be inline-able because one
might one day use a regexp for example.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
I think security definer functions should automatically inherit their
search_path. The whole secure by default thing.
This assumes that the search path at creation time has something to do
with the path you'd like
)
postgres=# select * from b;
i
---
2
3
(2 rows)
postgres=# select * from a full outer join b on (a.i=b.i) where a.i is null or
b.i is null;
i | i
---+---
1 |
| 3
(2 rows)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
.
--
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
message can get
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark escribió:
I think it would be ok only if a pg_dump/pg_restore reliably restored the
same
oid-enum value mapping. Otherwise a binary dump is useless. But as I
understand it that's the case currently, is it?
er, lost
I wouldn't be confident that all operating
systems do so or that they work correctly in all circumstances.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
Andrew Sullivan [EMAIL PROTECTED] writes:
On Fri, Aug 31, 2007 at 07:07:40PM +0100, Gregory Stark wrote:
It shouldn't be easy. Ident uses TCP, which is rather harder to
spoof.
Say what? It's actually quite easy to spoof TCP. There are even command-line
tools to do it available
and then cached for subsequent accesses. So xid_age() would
measure relative to a fixed xid, it just wouldn't be *our* xid necessarily.
Just a thought.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4
in the release
announcement as possible compatibility gotchas is what's needed.
--
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
into the internal representation? When you run
a query like WHERE '...' @@ col if there wasn't a tsquery data type then
'...' would have to be parsed over and over again for each row.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end
someone else created the same
file name you'll delete the wrong file?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating
Bruce Momjian [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
There is no question things would be clearer with only one text search
data type. The only value I can see to having a tsquery data type is
that you can store a tsquery value
didn't specify a tablespace.
--
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
)));
! else if (MyProc-waitStatus == STATUS_OK)
! ereport(LOG,
! (errmsg(process %d acquired %s on %s after %ld.%03d ms,
! MyProcPid, modename, buf.data,
! msecs, usecs)));
! pfree(buf.data);
}
} while (MyProc-waitStatus == STATUS_WAITING);
--
Gregory
. There are always going
to be cases where it could help.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ends. I have a hunch but I guess it would
take experiments to get a real answer. And the answer might be very different
on different OSes and hardware configurations.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
. It didn't even affect the 95th percentile. I think
you had to look at the 99th percentile before it even began to impact the
results.
I can't really imagine a web site operator being happy if he was told that
only 1% of user's clicks resulted in a browser timeout...
--
Gregory Stark
to remove it
instead of fix it --- it really has no excuse to live when we support
IN (sub-SELECT) constructs.
Comments?
Wow, those are strange beasts.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
it was their own fault and put in
aliases in their queries.
--
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
steps?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Note that if you use something like fetchrow_hashref it will actually
condense
out duplicate column names since it loads the row into a hash. So if you
you're writing a program which just wants to dump the record
Zeugswetter Andreas ADI SD [EMAIL PROTECTED] writes:
how much harder can it be to accept:
group by 'foo'
Presumably you meant group by foo.
No that's the whole point. He meant the constant string 'foo' not the column
identifier foo which certainly should work now.
--
Gregory Stark
truly pointless.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark escribió:
The upside is the convenience which after all is the same upside as most of
our spec grammar extensions. Many many programmers are accustomed to entering
ad-hoc queries of this form and forcing them to enter an alias
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
This seems like a particularly petty case compared to a lot of other
extensions we do allow.
That's exactly the problem. Most of our other extensions are justified
by some significant capability gain. This isn't
updating
the configuration's mappings.
I'm not really up-to-date on all this tsearch stuff. What would happen if you
already had a parser but wanted to fix a bug or add one new feature or
something like that?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
DISTINCT ON feature.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
, 16430, 0, 16777216, 2, 0,
2520930944, 0, 2520930944, 0, 2520914784, 0, 2520914784,
0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 1, 0, 0, 0, 0, 0, 0, 0}}}
(gdb) p MyProc-ShmemBase
$3 = (PGPROC *) 0xff9ac36e36e264b8
(gdb) p (unsigned long)MyProc-ShmemBase
$4 = 2520941752
--
Gregory Stark
by avoiding the need for
individual backends to evict dirty pages. So it would be interesting to know
with 8.3 whether the average response time even outside of checkpoints is
reduced by having a more aggressive bgwriter policy.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
along and deletes both the original source record and the
target record before you've gotten around to inserting the new record...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain
instead of going through the executor. As long as the record
is still there with the same xmin then we now the value we cached for it is
still valid. This would help the OLTP case where you're performing many small
transactions which refer to the same records over and over again.
--
Gregory
it back to read-only. It does have the one more knob
nature though.
--
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
= makeNode(A_Const);
n-val.type = T_Integer;
n-val.val.ival = 1;
$$ = list_make3($1, (Node *) n,
makeTypeCast($2, SystemTypeName(int4)));
}
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark wrote:
I switched the code over to the sysv_sema style api. It's gotten a bit grotty
and I would clean it up if it weren't a temporary test program. If we find a
real problem perhaps I should add a test case like this to the smoke test
Heikki Linnakangas [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
That general approach of storing a common part leading part just once is
called prefix compression. Yeah, it helps a lot on long text fields.
Tree structures like file paths
ON tblname USING gin (to_tsvector('config', textcolumn));
Is there a null configuration which could be the default for the casts? So the
syntax would still work and would generate an index which worked well but has
no stop words, no stemming, etc?
--
Gregory Stark
EnterpriseDB http
| Type | Modifiers
+-+---
i | integer |
a | integer |
View definition:
SELECT test.i, foo.a(test.i) AS a
FROM foo.test;
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
to check
the visibility.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
.
Numeric could store the a value relative to the parent value. Arrays could
store only the elements needed. bytea of course works just as well as text (or
better in the face of i18n).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
.
And if the overall table is large enough and you're dropping and loading
partitions then you may still be benefiting from partitioning by keeping all
the loaded records together and allowing dropping a partition to be constant
time.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
it could.
. add an ifdef USE_ASSERT_CHECKING which randomly fails to update the LSN when
syncing WAL so that even after a buffer flush we still can't set hint bits.
Only the first one isn't really wacky, but perhaps there's something there.
--
Gregory Stark
EnterpriseDB http
create a new type
would effectively do the same thing.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
when LP_DELETE is set?).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Seems to me this proves nothing much, since it doesn't use the same SysV
semaphore API PG does.
I was trying to copy the semaphore API exactly assuming
USE_NAMED_POSIX_SEMAPHORES
if I use the same operator directly on the text column? Or
perhaps it's not even possible to specify stop-words when operating on a text
column? Should it be?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
types.
--
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
supposed to be 100% reliable and have
indistinguishable behaviour barring a system crash and nobody should be
running production data on a beta or pre-beta build, so they should never see
a difference.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Gregory Stark [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
We're seeing a problem where occasionally a process appears to be granted a
lock but miss its semaphore signal.
Kernel bug maybe
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
I've written a synthetic test program to check for lost semaphore wakeups.
Seems to me this proves nothing much, since it doesn't use the same SysV
semaphore API PG does. Please adjust so that it looks more like our
there wouldn't be.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
improve the probability you're making a judgement of the
probability that programmers will manage to maintain all those properties
consistently, not about the probability that the race will occur at run-time?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
suggests considering VACUUM REWRITE.
I would think this would be 8.4 stuff except if all we want it to do is a
straight noop alter table it's pretty trivial. The hardest part is coming up
with a name for it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
right that there's no way to make it technically
impossible to de-obfuscate. All you can do is make any casual observer pause
and decide to break your license agreement.
If you don't believe him, just as the DVDCCA...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
sure it meets everyone's needs, then
drop the old command.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
be cheaper.
On the other hand if it's not expensive and the columns change frequently but
the results don't then we might be doing a lot of work for nothing.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
We're seeing a problem where occasionally a process appears to be granted a
lock but miss its semaphore signal.
Kernel bug maybe? What's the platform?
It does sound like
in keeping with how it determines whether a tuple is eligible for a
HOT update in the first place.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
or aborted before the
log sync.
--
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
the number of dead
line pointers we need before we can recover a useful amount of space depends
on the ratio of line pointer size to tuple size.
Perhaps we should be gathering bytes of dead tuples in pg_stat not just
n_dead_tuples.
--
Gregory Stark
EnterpriseDB http
assuming others (Alvaro? :) agree.
--
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
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
I would also suggest raising the level of the DEBUG2 message indicating why
tables were chosen or not. At least to DEBUG1 if not to INFO.
It's not acceptable for autovacuum to be cluttering the log by default.
Well
connections once there
are only known-doomed clients left. Ie, behave as if we're shut down already
but not actually exit until all the known-doomed clients drain out.
I think I agree that option 3 sounds simpler though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
expect anything else, on this test.
I think the surprising thing was that it wasn't slower due to the extra cpu
spent pruning tuples.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget
and not COLD updates seems broken.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
We're seeing a problem where occasionally a process appears to be granted a
lock but miss its semaphore signal.
Kernel bug maybe? What's the platform?
It does sound like it given the way my description went. I
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Testers here were having a hard time constructing test cases to reach some
lines touched by the varvarlena patch. Upon further investigation I'm
convinced they're unreachable.
I'm not really happy with any
be
toasted at all suddenly gets all its fields compressed if you add one more
field which ends up being stored externally.)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0
it doesn't cost anything because they're empty. But I could easily see
situations where the toast tables could be quite large but not be receiving
any updates when the main table is receiving a large volume of updates on
other columns.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
a bit
tricky as it only happens in fairly long benchmark runs. It seems to happen
every few hours of running at 3000+ transactions per minute...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9
log_autovacuum_* parameters and possibly a master log_autovacuum parameter.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating
It looks like there are some DEBUG3 messages which would be useful but I don't
know of any convenient way to change the log level in autovacuum workers.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP
perhaps people might get them
confused with trace...
Sigh... and I swore I wouldn't get involved in any more name games...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched
Postgre.
I'm a bit mystified here. What exactly about this syntax is easier or faster?
You still have to list all the column names. It looks like it would require
just as much typing as the regular syntax, no?
Or is it that you get to reuse the same string you use for doing an update?
--
Gregory
prefer or both to patches. It would be good to get one or the other
done in 8.3 so that if I or anyone else implements the charting with for
pgadmin they can support 8.3 instead of having to wait until 8.4.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
*/
chunkdata = NULL;
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http
--
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
message can get
Greg Smith [EMAIL PROTECTED] writes:
On Wed, 25 Jul 2007, Gregory Stark wrote:
Does gentoo these days have binary packages? source packages do implicitly
require custom builds...
You can install with binaries now so it doesn't take forever to get started,
but the minute you're adding
.
--
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
message can get
like
pg_temp_nnn_toast or pg_toast_temp_nnn. Then functions like
isOtherTempNamespace() could still recognize these tables as temp.
It'd mean a bit more clutter in pg_namespace though.
Why not just in the same pg_temp namespace?
--
Gregory Stark
EnterpriseDB http
set up a standby database in the regression suite which
would give us some xlog coverage as well which is a critical portion of the
system the regression suite doesn't test at all.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
a huge fan of Debian but even with that I think for this
situation I would actually agree that Redhat is a better fit in that it's
canonical. You can tell someone else install Redhat vFoo and know they'll
have precisely the same set of packages with the same set of services running.
--
Gregory Stark
early :) The problem
if we try to calculate reasonable defaults like this is it makes it unclear
how to expose any knob for the user to adjust it if they need to.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
:)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
=2 loops=52)
- Seq Scan on interval_tbl i (cost=0.00..1.15 rows=3 width=16)
(actual time=0.016..0.051 rows=2 loops=1)
Filter: ((f1 = '00:00:00'::interval) AND (f1 =
'23:00:00'::interval))
Total runtime: 2.104 ms
(7 rows)
--
Gregory Stark
EnterpriseDB http
Tom Lane [EMAIL PROTECTED] writes:
Alvaro Herrera [EMAIL PROTECTED] writes:
Gregory Stark wrote:
What really has to happen is it should run analyze on all tables
together in a single transaction and commit all the new stats together.
Out-of-sync stats can be worse than out-of-date stats
before we trigger vacuum? I think 20% is way too high and 5% is
saner. I actually think it would be better even lower but would be ok with 5%.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You
. CLUSTER and
most varieties of ALTER suffer from this problem as well.
It does seem like the shortest path solution is just to get things working
first with a one big lock implementation and then work on refining it after
that.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
there are user-space functions that can't leak memory. I'm sure everyone
knows about btree operators, but pgsql also assumes that type input and output
functions don't leak memory too (or else assignment leaks memory in the
function scope memory context and in a loop...).
--
Gregory Stark
pg_class and pg_attribute anyways so this doesn't seem
like a big deal.
But I thought I would mention it in case anyone else is offended or knows of a
more serious problem it could cause.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end
.
--
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 datatypes do not
match
using the connection string which may be
appropriate for a user-oriented application like psql. But in the general case
surely the application needs to be able to control the authentication process
and be able to provide credentials of its choice?
--
Gregory Stark
EnterpriseDB http
--- Makefile.linux 9 Dec 2005 21:19:36 - 1.22
+++ Makefile.linux 17 Jul 2007 05:52:43 -
@@ -11,6 +11,6 @@
endif
%.so: %.o
- $(CC) -shared -o $@ $
+ $(CC) $(CFLAGS) -shared -o $@ $
sqlmansect = 7
--
Gregory Stark
EnterpriseDB http
of this we can really measure though. Are there any other
events having an insufficiently large or excessively large value of this
parameter will cause which we can count?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
,
ControlFile-system_identifier);
It's possible I've done the autoconf hackery wrong though. Should
UINT64_FORMAT still be defined if there's no int64?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
will be which sets of operators and functions
become necessary to have operator classes for indexes.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
1001 - 1100 of 1641 matches
Mail list logo
