Gaetano Mendola [EMAIL PROTECTED] writes:
The count(*) information can be revisioned too, am I wrong ? I'm able to
create a trigger that store the count(*) information in a special table,
why not implement the same in a way builded in ?
Then every insert or delete would have to lock that
Lamar Owen [EMAIL PROTECTED] writes:
So, no, -fPIC does not appear to be required for libpq.
My understanding was that at least on some platforms once you need -fPIC for
some libraries you need to make sure they were all compiled with it. That
means it's a pain if any libraries are provided
Neil Conway kirjutas P, 30.11.2003 kell 02:18:
Jonathan Gardner [EMAIL PROTECTED] writes:
3) We would implement some sort of differential view update scheme
based on the paper Efficiently Updating Materialized Views[1].
Maybe the TelegraphCQ engine can give some ideas
Greg Stark writes:
My understanding was that at least on some platforms once you need -fPIC for
some libraries you need to make sure they were all compiled with it. That
means it's a pain if any libraries are provided compiled with -fpic because
whenever find one that reaches that threshold
Strange --- I have not seen it either.
---
Joe Conway wrote:
Bruce Momjian wrote:
I have loaded the patch queue with all patches that were in my main
mailbox:
http://momjian.postgresql.org/cgi-bin/pgpatches
OK, I emailed him telling him you had a newer version and would email
him back once it is applied.
Basic patch application is:
notify reviewers patch will be applied shortly
make sure patch is easily retrievable by reviewers
apply patch
run tools/pgtest (checks
Joe Conway [EMAIL PROTECTED] writes:
I posted an alternative to this one
http://candle.pha.pa.us/mhonarc/patches/msg4.html
for comment last night (however I can't find it in the archives -- I'll
paste it below). I was going to commit it tomorrow if I don't hear any
objections.
Looks
Hello, my name is Diego Montenegro, I am an M.S. student at Yale
University, and I am taking a project course with Prof. Avi Silberschatz
next semester, and I wanted to develop something for postgreSQL.
I wanted some suggestions, on projects (ITEMS) from the TODO list, that
can be done in a 4
Tom Lane wrote:
Yes. Please commit to 7.3 branch before Tuesday noon so it gets into
7.3.5 (or if you can't make that, let me know and we'll work something
out).
Done.
Joe
---(end of broadcast)---
TIP 7: don't forget to increase your free space
Hannu == Hannu Krosing [EMAIL PROTECTED] writes:
Hannu Neil Conway kirjutas P, 30.11.2003 kell 02:18:
Jonathan Gardner [EMAIL PROTECTED] writes: 3) We
would implement some sort of differential view update scheme
based on the paper Efficiently Updating Materialized
On Wed, 2003-11-26 at 05:53, Tom Lane wrote:
Grzegorz Dostatni [EMAIL PROTECTED] writes:
Currently the datase is roughly 80 Megs. About half of
the size is stored in pg_xlog directory. I managed to
figure out that those files are transaction log files?
How can I delete them safely?
You
Oliver Elphick [EMAIL PROTECTED] writes:
The use of the word log in the directory name does tend to invite
this error, and some have acted on it without asking first. I think
initdb should put a README.IMPORTANT file in $PGDATA to say [...]
If someone deletes something from $PGDATA without
Per this gripe:
http://archives.postgresql.org/pgsql-bugs/2003-11/msg00233.php
I think that the recent IPv6 changes made an undocumented and
un-agreed-to change in the semantics of netmask().
The previous behavior of netmask() was that it always delivered
a result with a masklen of 32. It seems
Tom Lane wrote:
The previous behavior had been agreed to at one point:
http://archives.postgresql.org/pgsql-hackers/2000-10/msg01132.php
I can't find anyplace in the archives where the change was discussed
at all.
hostmask() was not in 7.3 so its behavior is a bit up for grabs,
but I think
Here is an email on the open issues.
---
Ron Mayer wrote:
Tom wrote...
At this point it should move to pghackers, I think.
Background for pghackers first, open issues below...
Over on pgpatches we've been
Hi, all!
I'm preparing new release of uniqueidentifier datatype. In new relaease
in addition to existing btree operator class I've implemented hash
operator class. But what class should be default for this datatype?
Uniqueidentifier is used for identification, so main operation with it
is '=', on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've seen a lot about partitions recently, and I had a bright idea. I am
by no means a database expert, so perhaps this is utter nonsense.
A partition, as I understand it, contains only a select subset of a table.
Usually, it is data that is
Bruce Momjian [EMAIL PROTECTED] writes:
If qsort is to blame, then maybe this patch could help. It sorts
equal key values on item pointer. And if it doesn't help index
creation speed, at least the resulting index has better correlation.
I will try to apply it within the next 48 hours.
I
Patch removed from queue.
---
Manfred Koizar wrote:
On Mon, 01 Sep 2003 08:46:09 -0400, Tom Lane [EMAIL PROTECTED]
wrote:
[EMAIL PROTECTED] writes:
it took 69 minutes to finish, 75% of this time was devoted to create 2
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
If qsort is to blame, then maybe this patch could help. It sorts
equal key values on item pointer. And if it doesn't help index
creation speed, at least the resulting index has better correlation.
I will try to apply it within
On Mon, Dec 01, 2003 at 09:38:06AM +1100, Alex Satrapa wrote:
create or replace function get_transactions (INTEGER) returns set of
record as '
DECLARE
cust_id ALIAS FOR $1;
BEGIN
for r in select ... from ... loop
return next r;
end loop;
return;
END
' language 'plpgsql';
But
Alvaro Herrera wrote:
Me too. I've created many functions to extract data that are joined to
other functions. All in all the result is not as optimal as it could
be, because the optimizer can not poke into the functions, and the
estimates about functions are only guesses. If one could use
22 matches
Mail list logo
