it.
Have anice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
to pg_dump should do what you want.
snip
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
on a 64-bit arch, how else is it going to hold
the pointer for a pass-by-ref value?
On the whole, PostgreSQL is still in the phase where we're trying to
find the best algorithms. When that's done (if ever), we can start
worrying about processor optimisations...
Have a nice day,
--
Martijn van
at tackling them, I can
provide an updated list.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
this to declare
a dependancy on them all?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
would suck :)
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
when it hit a particular function.
By selecting different functions each time, once you'd covered a lot of
functions and tested recovery, you could have a good idea if the
recovery code works properly.
Has anyone seens a tool like that?
Have a nice day,
--
Martijn van Oosterhout kleptog
are
zero-cost.
A more useful definition of fragmentation would be: if you're scanning
forward through an index, how often do you have to jump backwards
again. The current calculation seems to get that fairly right...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org
On Thu, Aug 17, 2006 at 02:54:20PM -0500, Jim C. Nasby wrote:
On Thu, Aug 17, 2006 at 02:23:48PM +0200, Martijn van Oosterhout wrote:
On Thu, Aug 17, 2006 at 12:55:28PM +0900, ITAGAKI Takahiro wrote:
But the method has the above problem. So I suggest to use whether
the right link points
a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
On Thu, Apr 20, 2006 at 11:56:32AM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
About the only thing in the backend I found interesting was this:
src/backend/utils/hash/dynahash.c function hash_create
I wonder if we shouldn't just remove the hash_destroy calls
... Or perhaps at the end of the initdb?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
?
Well sort of. I can also just tick a box and the warning goes away too.
It just seemed from the discussion that it was something people were
going to fix...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each
opinions about that...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
further down. They mark it as line 3956 of revision 1.335.
It may not be possible though, coverity is not omnicient.
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
)
and I have not seen any discussion about it since March or so.
Unfortunatly I agree. I was kinda prepared to have a shot at
resurrecting the patch if there was some serious interest but nothing
happened.
It's way too late in the freeze now. There's still 8.3...
Have a nice day,
--
Martijn van
the casts, but it's user friendly to
do so. Requiring double casts to go between two essentially compatable
types seems silly...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
installed by a package, thus dispensing
with the pg_package_items. The biggest stumbling block was finding
something general enough. Oh yeah, and coding it. In particular,
consider being able to install stuff in contrib as a package, so you
can easily uninstall it.
Have a nice day,
--
Martijn van
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
could make a tool that
would scan the queries and tables that look for column combinations
which are often joined and have an unusual correlation (unusually high
or unusually low).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
to the other will have it's
own pitfalls...
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
On Tue, Aug 08, 2006 at 04:14:45PM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
ISTM theat the easiest way would be to introduce a sort of predicate
like so:
SELECT * FROM foo, bar WHERE pg_selectivity(foo.a = bar.a, 0.1);
The one saving grace of Florian's
it easiesr.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
( a TEXT IN, b TEXT INOUT, c TEXT OUT ) as blah...
And in a pl/pgsql function, translate: CALL foo(a,b,c)
into (b,c) = foo(a,b) internally.
Doesn't seem like that would be too hard.
Have anice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
) the ability for someone to pick up where you left off.
That I can agree with, but I don't think you can force it.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
: fast tree drift :) But I guess
you can't really complain about that.
Oh yeah, user-defined typmod would be cool. There's some movement on
that though.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
, there are the priveledged few who are being paid to work on
postgres. If you can convince their employers to fund things on the
list, it might help. Also, some stuff might work well as Google SoC
projects...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From
.
Submit a patch to the patches list, where it will be reveiwed by the
relevenet people.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital
PROTECTED] so that your
message can get through to the mailing list cleanly
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
can be specified the same way as
for numeric.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
be to merge the productions for types
and functions. Or at least, make the productions look similar enough
that bison can avoid deciding which it is until it's got past the whole
definition.
Habe a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according
? If there's a
limit you're not really superuser, are you?
Slony in particular does not need more than N connections but does
require being a super user.
Maybe someone should look into enabling slony to not run as a
superuser?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http
: this is what I remember about the discussions anyway.
I'm sure a lot of people would be happy if someone took this on though.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate
version...
Have an nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
a very very useful
one.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
install
C code into the backend and break security are truisms: installed C
code can do *anything* which is why only superusers can install such
functions...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according
want to be sure you are not bypassing security checks,
use the SPI interface.
Would that help? You're talking about the schema check as if it's a
special case, but when people use low-level functions they have to
check *everything* themselves.
Have a nice day,
--
Martijn van Oosterhout kleptog
heard of it. It's not taught in schools which pretty much means it's
never going to happen. When manufacturers like Dell start using KiB in
their glossy magazines, maybe it's time to look into it.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From
it in the rink.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
On Wed, Jul 26, 2006 at 11:37:01AM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
Well, my only thoughtis that this pretty means you can't use
index_getmulti for anything else. For example, when I was playing with
async i/o I was using index_getmulti to get a list
in postgres where using K=1000 would be significantly
clearer than K=1024?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
excruciating pain for the DBA.
I thought the suggested solution for that was the dead space map. That
way vacuum can ignore parts of the table that havn't changed...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability
fix this
one.
We should probably move the probes file to a subdirectory. Anyone know
a good place?
Also, again, the pgsql prefix should be dropped.
The prefix here is redundant. We know which directory it's in.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http
://www.geocities.com/mailsoftware42/db/
http://www.devx.com/dbzone/Article/29480?trk=DXRSS_DB
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital
silent_mode is on. I think it defaults to off, which is
probably why it works at all.
Anyway, the signal handling for Windows involves a seperate thead AIUI
which may make it easier. It might be interesting to see how bash does
it.
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org
to be limiting you to
one installation per machine.
Setting the PATH would probably work too.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description
the script gets updated with the
appropriate CVS tag and you're done.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
you the size of
of the C datatypes if you're interested :)
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
as well as a program. It returns the os name, version,
hostname and system type.
Mind you, maybe perl provides emulation for uname?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
to build more than just the core among their
standard packages.
Ack.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
guess we could
invent a comment that would be machine readable.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
as we disired.
How can ShmemBase not be aligned? Surely it's page-aligned?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
in Perl that can decode most tuples, but
not all. It fails because it doesn't recognise all the types.
http://svana.org/kleptog/pgsql/pgfsck.html
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his
records, like you originally
suggested.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
the effects of included
header files, but it would pick up the cases where a block of code that
was previously included no longer is. Or if a macro is expanded
differently...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his
of its add-ins, though that seems presumptious.
The easiest way is to simply delete the shared memory segment after
you've done the shmat(). The shmat() will hold onto it until postgres
quits and then be cleaned up by the OS.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http
)? I grabbed that
from relation_open in access/heap/heapam.c.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
an extra step has to be taken.
This extra step copies the two values, creating a new tuple, which has
no CTID.
If you're tying yourself this tightly to the backend, maybe you should
just use index_beginscan/heap_beginscan/etc which return actual tuples.
Have a nice day,
--
Martijn van Oosterhout
On Mon, Jul 10, 2006 at 02:03:11AM +0300, Tzahi Fadida wrote:
On Monday 10 July 2006 00:29, Martijn van Oosterhout wrote:
On Sun, Jul 09, 2006 at 10:08:42PM +0300, Tzahi Fadida wrote:
They return format_type_be(INT4OID) = integer or
format_type_be(FLOAT8OID) = double precision
I need
day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
priveledges unless you're sure you want people to
have them.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
, the revoke should at the very least not affect transactions
started prior to the revokation. Some things are shared across an
entire session, and the rule extends to them. Is this a bug? Maybe, but
it is debatable.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org
.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
opinions aren't really that
relevent. Do other database systems work the way you expect?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital
| float8
--+
1 |4.5
(1 row)
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
a clue lies there...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
it's not really
necessary, there is currently nothing else in the system that really
tells you the answer to the question you ask...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
ofcourse.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
for it.
But this seems a little like premature optimisation. First, make it
work, then make it fast. Once you've got it working you can worry about
performance. Adding an extra column to the output costs very, very
little compared to other things...
--
Martijn van Oosterhout kleptog@svana.org http
involved, everything in the scankey
should already have been filled in. I don't beleive the code actually
checks if the operator is of the type you specify.
Hope this helps a bit,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each
.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
be replaced by any number, or even -1 to make a variable
length type...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
;
CREATE FUNCTION uuid_out(uuid) RETURNS cstring AS 'hex_raw_out' LANGUAGE
internal;
CREATE TYPE uuid (
input = uuid_in,
output = uuid_out,
internallength = 16
);
The cat lookups are irritating, but that's what syscache is for, I
guess :)
Have a nice day,
--
Martijn van Oosterhout kleptog
during parse time. This would give the type input/output
functions the Expr node they need to extract this info.
I have no idea how easy/hard this would be.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each
On Fri, Jun 30, 2006 at 04:04:19AM -0400, [EMAIL PROTECTED] wrote:
Martijn van Oosterhout wrote:
It seems to me that maybe the backend should include a 16-byte fixed
length object (after all, we've got 1, 2, 4 and 8 bytes already) and
then people can use that to build whatever they like
,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
idea, that of reusing dead
index entries ?
I'd like to know about this too, including ideas about truncating
tuples to just the header.
Have a nice day.
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his
.
And for people that want char(1), they should be using char, which
really is one byte (ex padding ofcourse).
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
On Thu, Jun 29, 2006 at 06:40:13PM +0200, Thomas Hallgren wrote:
Martijn van Oosterhout wrote:
On Thu, Jun 29, 2006 at 03:54:36PM +0200, Thomas Hallgren wrote:
I have to concur with this. Assume you use a bytea for a UUID that in
turn is used as a primary key. The extra overhead
that it
only tries to write out pages not recently used, so hopefully there
would be very little contention there.
And perhaps you can avoid the xlogging for the same reason as I
suggested above.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each
people are working
on the same version.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
-compatible with the input datatypes. Do not use this if
* you need an exact- or binary-compatible match; see compatible_oper.
...etc...
Hope this helps,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
at that block might help identify the
issue.
Have a ncie day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description: Digital signature
the BitmapAnd will incorrectly throw them out.
That should be doable, if you only change the head of the SITC on
VACUUM. I'm not sure if that's what's being suggested right now.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability
there's a difficiency in Windows TCP code. Do you have any
benchmarks to show this actually makes a difference. According to the
URL you give, the problem occurs if the libpq buffer is *bigger* than
the socket buffer, which it isn't...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org
buffer at least 1 byte bigger.
Ok, but even then, are there any benchmarks to show it makes a
difference. The articles suggests there should be but it would be nice
to see how much difference it makes...
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog
quite a bit of coding by
adding a pqHaveNBytes function that returns true if there are that many
bytes available. Then right after you know the number of attributes,
you can do a pqHaveNBytes(4*nattr) and skip the checking within the
loop.
Have a nice day,
--
Martijn van Oosterhout kleptog
? And for bitmap index scans you would only remember the page in
the case of such a tuple, since you can't be sure the exact ctid you've
got is the one you want.
Seems doable.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each
in the backend after the
SeqScan/IndexScan node really don't care about most of the header
fields and being able to drop them would be nice.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
confused where bitmap index scan fit into all of this. Is
preserving the sequential scan aspect of these a goal with this new
setup?
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability
can always find the newest version. You would need to add additional
links to go backwards.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according to his ability to
litigate.
signature.asc
Description
the other end. In indexes, allow a row to
carry multiple CTIDs. That way a new version only requires adding six
more bytes, rather than a whole new tuple.
Have a nice day,
--
Martijn van Oosterhout kleptog@svana.org http://svana.org/kleptog/
From each according to his ability. To each according
801 - 900 of 1563 matches
Mail list logo
