As luck would have I've put some thought into this problem before as
well. Having reviewed the code quite a bit, and played around with the
backend, my intuition tells me that the following would work.
Write a custom "cluster-aware" postmaster so it distributes queries to
various machines. Of
"Hans-Jürgen Schönig" <[EMAIL PROTECTED]> wrote:
> We have used Peter's fix which makes it possible to compile PostgreSQL
> with Intel's C compiler. PostgreSQL built nicely (just some nasty
> warnings). We have tries to run our benchmark (mostly simple statements
> and cursor work) on this version
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> but after that it checks proc->xmin, where xmin may not be running on
> the same database. I wonder if this is correct or not. Maybe we should
> make sure that xmin is running on the same database
How would you know? (At the time you are looking, it's qu
I think you are right about this. When people look up a
timezone, what we see is the offset to UTC.
UTC + (offset) should equal current time.
We should be consistent. And since the timestamp with
timezone is relatively recent, maybe it will not be so painful
to change the behaviour of extra
On 3 Jul 2003 at 13:18, Tom Lane wrote:
> Comments?
The message headers for this email contained:
Received: from www.postgresql.com (www.postgresql.com
[64.117.225.209])
by m20.unixathome.org (Postfix) with ESMTP id 77EC27A69
for <[EMAIL PROTECTED]>; Thu, 3 Jul 2003 15:33:13 -0
Hello,
> We share the same ideas. Please refer to (CVS is down at the
> moment) :
> http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/*checkout*/pgadmin3
>/docs/en_US/translation_guidelines.html
Just a little french mistake at the end of the document :
>Do not choose distant words, like "déclancheur"
On 02-Jul-2003, 10:55, Dave Page <[EMAIL PROTECTED]> wrote:
As many of you already know, pgAdmin is a widely used Open Source GUI
Management tool for PostgreSQL, similar to DB2's Control Center or SQL
Server's Enterprise Manager.
[snip]
In addition to full Unicode support, we also aim to translate
Being new to Postgres, I understand how frustrating tuning is. I've been
working on some very basic queries, and trying to get some decent performance.
I know the problem isn't with io on the system, since I can use other tests
that far exceed the amount of data being written through postgres, so I
This week I have done some performance tuning at a customer's office. We
have beaten (demoralized) MS SQL and DB2 in serializable mode and DB2 in
any transaction isolation level :).
By the way: In case of very simple statements SERIALIZABLE is about 3
times faster than READ COMMITTED. I expecte
> > Does anybody know why vacuum full does not relcaim deleted rows if a
> > open transaction which started before the deletion happens is running
> > even on a different database?
>
> On what do you base that it doesn't reclaim those rows?
test=# vacuum full verbose t1;
INFO: --Relation public.
On Sun, Jul 06, 2003 at 12:00:39AM +0900, Tatsuo Ishii wrote:
> Hi,
>
> Does anybody know why vacuum full does not relcaim deleted rows if a
> open transaction which started before the deletion happens is running
> even on a different database?
On what do you base that it doesn't reclaim those ro
Hi,
Does anybody know why vacuum full does not relcaim deleted rows if a
open transaction which started before the deletion happens is running
even on a different database?
Here is an example:
T1: psql db1
T2: psql db2
T3: psql db2
T2: create table t1(i int); insert into t1 values(1);
T1: begin
Chris,
would be the right solution to make tsearch V2 to be fully incompatible
with old tsearch (so both version could live in one database) and
release tsearch v2 in separate directory. This way require some additional
work but would not confuse people. As a bonus, people could start playing
with
On 4 Jul 2003 at 23:22, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> > Now that my NZ server is up and running:
> > template1=# select now();
> > 2003-07-05 12:47:15.444535+12
>
> > That doesn't look backwards to me.
>
> Try EXTRACT(timezone_hour from now());
>
> The timestam
14 matches
Mail list logo
