Hannu Krosing <[EMAIL PROTECTED]> writes:
> How about adding a new 2-byte field to header for in-page c_tid poiner
> for HOT ?
We just finished sweating blood to get the tuple header size down to 23
bytes from 27 (which saves 8 bytes not 4 if MAXALIGN=8). We are not
going to blow that again on HO
I wrote:
>> * Add an oid[] column to pg_constraint that stores the equality operator
>> OIDs for a foreign-key constraint, in the same column order as conkey[]
>> and confkey[].
It turns out this isn't sufficient: ri_Check_Pk_Match() wants to
generate PK = PK checks, and the PK = FK operator isn't
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> and why is this a feature? i mean, what real use it has?
To find out the parameters of an existing sequence. Remove it and
you'll break pg_dump, to say nothing of any other application.
regards, tom lane
Marc Munro <[EMAIL PROTECTED]> writes:
> Consider a table C containing 2 child records C1 and C2, of parent P.
> If transaction T1 updates C1 and C2, the locking order of the the
> records will be C1, P, C2. Another transaction, T2, that attempts to
> update only C2, will lock the records in order
"D'Arcy J.M. Cain" writes:
> Well, that is covered in the system that I took that from. The full
> description is;
> 1. Identify a bug or missing feature.
> 2. Write the test that proves the bug or missing feature.
> 3. Run the test to prove that it fails.
> 4. Code until the test passes and
On 2/11/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> just for curiosity, why the code doesn't throw an error when using
> sequences in the from_list of a select?
That's a feature, not a bug.
and why is this a feature? i mean, what real use it has?
--
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> just for curiosity, why the code doesn't throw an error when using
> sequences in the from_list of a select?
That's a feature, not a bug.
regards, tom lane
---(end of broadcast)
Hi,
just for curiosity, why the code doesn't throw an error when using
sequences in the from_list of a select?
allow selects from sequences confuses many people about the correct
way of using sequences
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving
On 2/12/07, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
Hannu Krosing wrote:
> Ühel kenal päeval, P, 2007-02-11 kell 12:35, kirjutas Tom Lane:
>> Hannu Krosing <[EMAIL PROTECTED]> writes:
>>> What if we would just reuse the root tuple directly instead of turning
>>> it into a stub ?
>>> This w
I have a project I'm working on that involves a deep look at WAL and
checkpoint performance; a patch related to this topic will be ready to
release shortly. The company I'm working for was kind enough to allow me
to release the documentation I wrote for them while trying to understand
the code
On Sun, 2007-11-02 at 12:21 -0600, Jim C. Nasby wrote:
> On Thu, Feb 08, 2007 at 08:47:42AM -0800, Marc Munro wrote:
> > One of the causes of deadlocks in Postgres is that its referential
> > integrity triggers can take locks in inconsistent orders. Generally a
> > child record will be locked befo
On Sun, 11 Feb 2007 12:30:45 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> "D'Arcy J.M. Cain" writes:
> > How about a rule that says no new ode without a test?
>
> We've got way too many tests like that already, ie, a bunch of
> mostly-redundant functional tests of isolated new features.
> Most of
Hannu Krosing wrote:
Ühel kenal päeval, P, 2007-02-11 kell 12:35, kirjutas Tom Lane:
Hannu Krosing <[EMAIL PROTECTED]> writes:
What if we would just reuse the root tuple directly instead of turning
it into a stub ?
This would create a cycle of ctid pointers, which changes the lookup
process fro
Sorry All,
I go to see another list.
Cris.
On 2/11/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Cristiano Panvel wrote:
> This is my first post in the list.
This list is for discussing the development of PostgreSQL. Please take
your usage questions to a different list.
http://www.postgre
Cristiano Panvel wrote:
> This is my first post in the list.
This list is for discussing the development of PostgreSQL. Please take
your usage questions to a different list.
http://www.postgresql.org/community/lists/
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
Hi Friends,
This is my first post in the list.
I am not obtaining authentication my users of PostgreSQL in OpenLdap.
1) PostgreSQL was compiled with the support to ldap in a FreeBSD System.
"option --with-ldap for configure".
2) The user also exists in the base of the OpenLdap
3) Alre
Pavan Deolasee wrote:
On 2/11/07, Hannu Krosing <[EMAIL PROTECTED]> wrote:
Ühel kenal päeval, P, 2007-02-11 kell 12:35, kirjutas Tom Lane:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > What if we would just reuse the root tuple directly instead of
turning
> > it into a stub ?
> > This would
Peter Eisentraut wrote:
> [EMAIL PROTECTED] wrote:
> > I think we had this discussion already. strncpy() copies N bytes,
> > whereas strlcpy() copies only as many bytes as necessary. For short
> > strings with larger buffers, strlcpy() wins. It's understood that
> > in many cases in PostgreSQL, the
Pavel Stehule wrote:
Postponed
The following features are unlikely to make it into 8.3 at this point:
* SQL/PSM support per SQL:2003 (Pavel)
* Clustered/replication solutions
SQL/PSM is available (without resignal stmt and extended diagnostic stmt).
Some people work on doc translation
Pavel Stehule wrote:
Postponed
The following features are unlikely to make it into 8.3 at this point:
* SQL/PSM support per SQL:2003 (Pavel)
* Clustered/replication solutions
SQL/PSM is available (without resignal stmt and extended diagnostic
stmt). Some people work on doc translation
On 2/11/07, Hannu Krosing <[EMAIL PROTECTED]> wrote:
Ühel kenal päeval, P, 2007-02-11 kell 12:35, kirjutas Tom Lane:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > What if we would just reuse the root tuple directly instead of turning
> > it into a stub ?
> > This would create a cycle of ctid p
On Thu, Feb 08, 2007 at 08:47:42AM -0800, Marc Munro wrote:
> One of the causes of deadlocks in Postgres is that its referential
> integrity triggers can take locks in inconsistent orders. Generally a
> child record will be locked before its parent, but not in all cases.
Where would PostgreSQL lo
Ühel kenal päeval, P, 2007-02-11 kell 12:35, kirjutas Tom Lane:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > What if we would just reuse the root tuple directly instead of turning
> > it into a stub ?
> > This would create a cycle of ctid pointers, which changes the lookup
> > process from 'foll
Hannu Krosing <[EMAIL PROTECTED]> writes:
> What if we would just reuse the root tuple directly instead of turning
> it into a stub ?
> This would create a cycle of ctid pointers, which changes the lookup
> process from 'follow ctid chaint until the end' to 'follow the tid chain
> until you reach t
"D'Arcy J.M. Cain" writes:
> How about a rule that says no new ode without a test?
We've got way too many tests like that already, ie, a bunch of
mostly-redundant functional tests of isolated new features.
Most of the code I worry about there isn't any simple way to
test from the SQL level --- th
Tom and all,
I apologize destroying the thread information with this topic.
Unfortunately my basic smtp server does not work now and I am writing
all the responses via gmail tonight...
Tom,
Thanks for teaching me about the development assumption of PostgreSQL.
The assumption and my direction ar
Tom,
Thanks for your comments !
Let me answer to your beneficial mail.
Indeed, I'm wondering why one needs to hack the Postgres core to throw
away data integrity guarantees;
The motivation of my work is accelerating INSERT/UPDATE without losing
data integrity guarantees. In the first place, I
Andrew,
Your experience is really informative. Thanks for giving me such a
really precious information. Since I am a researcher, I rarely faces
on real troubles.
Andrew, I agree with you. UPS is not reliable all the time.
On the other hand, however, disks or raids are also not reliable all the t
Magnus Hagander wrote:
> On Tue, Jan 30, 2007 at 11:45:24AM -0500, Tom Lane wrote:
>> Magnus Hagander <[EMAIL PROTECTED]> writes:
>>> But I guess maybe the added check has to be not just (!syslogger_started)
>>> but (!syslogger_started && is_postmaster)?
>> That would at least get you out of the pr
Christopher,
Thanks for your advices !
OK, I will submit a patch as soon as possible.
In the patch, Sigres will be activated by postgresql.conf.
Best Regards,
-- Hideyuki
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED]
(Hideyuki Kawashima) wrote:
> I appreciate your great sug
Christopher,
Thanks for your comments and I am sorry for my bad response because of
my business. In the first place, criticisms are welcome since without
criticisms and discussions, I cannot improve my idea.
Christopher, thanks to your comments, I understood why this community
does not incline t
Tino Wildenhain wrote:
> >
> > linda
> > 19
> > (0.9,6.1)
> > 100
> >
^
> >
> How would you express null in the values above?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadc
Peter Eisentraut schrieb:
The issue of XML export has been discussed a few times throughout
history. Right now you've got the HTML output in psql. A few
people have proposed "real" XML output formats in psql or elsewhere.
I dug out some old code today that implements what SQL/XML has to say
on
On Sat, 10 Feb 2007 10:36:56 +0100
Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
> > I'm not concerned so much about the runtime as the development and
> > maintenance effort...
>
> Shouldn't we at least add the one or two exemplary statements that
> failed so we have some sort of
Pavel Stehule wrote:
> I thought about some special function. But why not? COPY is perfect
> for this task.
I don't understand what you are asking for. Please show an example.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)
Postponed
The following features are unlikely to make it into 8.3 at this point:
* SQL/PSM support per SQL:2003 (Pavel)
* Clustered/replication solutions
SQL/PSM is available (without resignal stmt and extended diagnostic stmt).
Some people work on doc translation to english.
experienc
Pavel Stehule wrote:
> If you integrate xml_export to core, you don't need string argument,
> which isn't too handy, but you can use COPY stmt aparat. I don't
> speak about enhancing stmt COPY.
Then what do you speak about?
I thought about some special function. But why not? COPY is perfect fo
Hi,
It is very good to see Magnus among committers. Congrats Magnus!
Cheers, Devrim
Forwarded Message
> From: Magnus Hagander <[EMAIL PROTECTED]>
> To: pgsql-committers@postgresql.org
> Subject: [COMMITTERS] pgsql: Fix for early log messages during
> postmaster startup getting
Aloha,
I just wanted to bring up the wishlist todo items:
http://developer.postgresql.org/index.php/Todo:WishlistFor83
All items have a name behind them aside from "Better handling of
partitioning". Does anyone feel responsible for handling that one?
Anyways I would appreciate it if people wh
On Sat, Feb 10, 2007 at 12:20:35PM -0500, Tom Lane wrote:
> I do
> agree with adding a test when you think it is likely to be able to catch
> a whole class of errors, or even a specific error if it seems especially
> likely to recur, but right now I'm not seeing how we do that here.
Well, current
[EMAIL PROTECTED] wrote:
> I think we had this discussion already. strncpy() copies N bytes,
> whereas strlcpy() copies only as many bytes as necessary. For short
> strings with larger buffers, strlcpy() wins. It's understood that
> in many cases in PostgreSQL, the expectation is for short strings,
Pavel Stehule wrote:
> If you integrate xml_export to core, you don't need string argument,
> which isn't too handy, but you can use COPY stmt aparat. I don't
> speak about enhancing stmt COPY.
Then what do you speak about?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
Hi,
Currently tsearch2 does not accept non ascii stop words if locale is
C. Included patches should fix the problem. Patches against PostgreSQL
8.2.3.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
*** wordparser/parser.c~2007-01-16 00:16:11.0 +0900
--- wordparser/parser.c 2007-02-10 18:04:59
Ühel kenal päeval, K, 2007-02-07 kell 17:38, kirjutas Simon Riggs:
> When we try to UPDATE a tuple and the new tuple version doesn't fit on
> the block, we get the BufferCleanupLock if possible and then perform a
> single-block VACUUM. Any tuple that is both HEAP_DEAD &
> HEAP_ONLY_TUPLE
> can be
Hello
If you integrate xml_export to core, you don't need string argument, which
isn't too handy, but you can use COPY stmt aparat. I don't speak about
enhancing stmt COPY.
Regards
Pavel Stehule
p.s.
it's can be great if xmloutput will be independent on datestyle
root=# set datestyle TO Germ
45 matches
Mail list logo
