* Sat 2008-01-05 Peter Eisentraut [EMAIL PROTECTED]
* Message-Id: [EMAIL PROTECTED]
Jari Aalto wrote:
Here is usggestion to add URL to documentation.
But there are other sources for the documentation. It might be
preferrable to use a local copy.
The local copy is not necessarily installed
Jari Aalto [EMAIL PROTECTED] writes:
* Sat 2008-01-05 Peter Eisentraut [EMAIL PROTECTED]
Furthermore I think it is fairly obvious that you can find
documentation on the website.
A direct URL will help ´people to head for right direction.
Somebody who has found postgresql.conf in the first
On Jan 6, 2008 3:00 AM, Robert Treat [EMAIL PROTECTED] wrote:
On Saturday 05 January 2008 14:02, Markus Schiltknecht wrote:
To satisfy all the different requirements of partitioning with
segments
based partitioning, we'd have to allow a table to span multiple table
spaces. I'm not very
On Jan 6, 2008 11:27 AM, [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jan 06, 2008 at 01:12:32AM +0530, Gokulakannan Somasundaram wrote:
On Jan 5, 2008 6:15 PM, [EMAIL PROTECTED] wrote:
One thought I had back then, with partitioned tables was gee --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I spent the better part of this evening tracking down a problem with a
high velocity database. The database had entered the point of no return
by invoking xidStopLimit.
This by itself isn't a problem because you just vacuum right? Well we
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I spent the better part of this evening tracking down a problem with a
high velocity database. The database had entered the point of no return
by invoking xidStopLimit.
8.2.4
Joshua D. Drake
Hi,
Gokulakannan Somasundaram wrote:
On Jan 5, 2008 6:15 PM, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
One thought I had back then, with partitioned tables was gee -- B-tree
index is already doing a partition; why do a manual partition on top of
that?.
Can you please
Hi,
Robert Treat wrote:
On Saturday 05 January 2008 14:02, Markus Schiltknecht wrote:
To satisfy all the different requirements of partitioning with segments
based partitioning, we'd have to allow a table to span multiple table
spaces. I'm not very keen on going that way.
Why?
Uh.. if a
On Jan 6, 2008 4:09 PM, Markus Schiltknecht [EMAIL PROTECTED] wrote:
Hi,
Gokulakannan Somasundaram wrote:
On Jan 5, 2008 6:15 PM, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
One thought I had back then, with partitioned tables was gee --
B-tree
index is already
On Jan 3, 2008 8:57 PM, Doug Knight [EMAIL PROTECTED] wrote:
All,
Is there a place where I can find information about tuning postgresql
running on a Windows XP Pro 32 bit system? I installed using the binary
installer. I am seeing a high page fault delta and total page faults for one
of the
jMartinez wrote:
Would it be possible to add an option to the pg 8.3 Windows installer to
separate the pg_log and pg_xlog folders from tha data one?
Both options already exist in 8.3; pg_log can be set in postgresql.conf
('log_directory') and pg_xlog can be set at initdb time.
--
Euler
Hi,
I changed the data type on a column (to an enum) but the previous
foreign key to the old table (replaced by the enum) is still accepted
event though the data types are now different. Is that the expected
behavior?
CREATE TABLE person_to_event (
id_person integer NOT NULL,
Louis-David Mitterrand wrote:
Hi,
I changed the data type on a column (to an enum) but the previous
foreign key to the old table (replaced by the enum) is still accepted
event though the data types are now different. Is that the expected
behavior?
CREATE TABLE person_to_event (
On Sun, Jan 06, 2008 at 10:18:35AM -0500, Andrew Dunstan wrote:
Louis-David Mitterrand wrote:
Hi,
I changed the data type on a column (to an enum) but the previous
foreign key to the old table (replaced by the enum) is still accepted
event though the data types are now different. Is
Andrew Dunstan [EMAIL PROTECTED] writes:
Louis-David Mitterrand wrote:
Hi,
I changed the data type on a column (to an enum) but the previous foreign key
to the old table (replaced by the enum) is still accepted event though the
data types are now different. Is that the expected behavior?
On Sun, Jan 06, 2008 at 04:07:40PM +, Gregory Stark wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Louis-David Mitterrand wrote:
Hi,
I changed the data type on a column (to an enum) but the previous foreign
key
to the old table (replaced by the enum) is still accepted event
On Sunday 06 January 2008 05:48, Markus Schiltknecht wrote:
What I'm saying is, that SE doesn't partition the segments into
different table spaces. Thus I don't consider it database partitioning
in the first place. As I currently understand it, it's:
table -- 1:1 -- table space -- 1:n --
Both options already exist in 8.3; pg_log can be set in postgresql.conf
'log_directory') and pg_xlog can be set at initdb time.
Yes, I know that, but I meant include the option directly in the msi
installer (which already let the user initialyse the db cluster) would be a
'nice to have'.
This
Sokolov Yura [EMAIL PROTECTED] writes:
create or replace function add_group(grp anyarray, ad anyelement, size int4)
returns anyarray
language plpgsql
...
create aggregate build_group(anyelement, int4) (
SFUNC= add_group,
STYPE = anyarray
);
ERROR: argument declared anyarray is not
Kevin Grittner [EMAIL PROTECTED] writes:
There was a serious performance regression in OUTER JOIN planning
going from 8.2.4 to 8.2.5. I know Tom came up with some patches to
mitigate the issues in 8.2.5, but my testing shows that problems
remain in 8.3beta4.
Please try the attached proposed
I tested 8.3beta4 with DBT-3 (TPC-H) and found unstable selection of plans.
Planner randomly selected two types of plans (A, B) when I repeated EXPLAIN.
One of the conditions is used in Seq Scan Filter in Plan A. In contrast,
the same condition is used in Hash Join filter in Plan B. Plan A is
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
I tested 8.3beta4 with DBT-3 (TPC-H) and found unstable selection of plans.
Planner randomly selected two types of plans (A, B) when I repeated EXPLAIN.
Are you sure the statistics weren't changing underneath you (due to
auto-vacuum or auto-analyze)?
Tom Lane [EMAIL PROTECTED] wrote:
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
I tested 8.3beta4 with DBT-3 (TPC-H) and found unstable selection of plans.
Planner randomly selected two types of plans (A, B) when I repeated EXPLAIN.
Are you sure the statistics weren't changing underneath
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
There might be regularity in the plan selection. When I connect to postgres
newly, I see plans { A, B, A, A ... }. Then disconnect, re-connect and send
the same EXPLAINs, the same pattern was reproduced.
Hmph ... maybe some effect associated with
Joshua D. Drake wrote:
Ping?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I spent the better part of this evening tracking down a problem with a
high velocity database. The database had entered the point of no return
by invoking xidStopLimit.
This by itself isn't a problem because
25 matches
Mail list logo
