"Tom Lane" <[EMAIL PROTECTED]> writes
>
> I very seriously doubt that there would be *any* win, and I doubt even
> more that it could possibly be worth the klugery you'd have to do to
> make it happen. Bear in mind that index access methods are two API
> layers away from md.c --- how will you tra
"Qingqing Zhou" <[EMAIL PROTECTED]> writes:
> Is there any performance benefits if we have a mdextend_several_pages()
> function in md.c?
I very seriously doubt that there would be *any* win, and I doubt even
more that it could possibly be worth the klugery you'd have to do to
make it happen. Bea
"Tom Lane" <[EMAIL PROTECTED]> writes
>
> Why bother? Just write each page when you need to --- there's no law
> that says you must use P_NEW. The hash index type does something pretty
> similar, IIRC.
>
Is there any performance benefits if we have a mdextend_several_pages()
function in md.c? S
"Victor Y. Yegorov" <[EMAIL PROTECTED]> writes:
> [ scheme involving a predetermined layout of index pages ]
> The question is: allocating pages this way is really ugly, I understand. Is
> there some API that would allow allocating N pages in the bulk way?
Why bother? Just write each page when y
BTW, I noticed that the "permission denied" messages throughout the
source don't quote the name of the identifier for which permission has
been denied. This violates the error code conventions: "Use quotes
always to delimit file names, user-supplied identifiers, and other
variables that might c
On Mon, Jun 06, 2005 at 09:23:21PM -0400, Bruce Momjian wrote:
>
> Is this a direction we want to explore --- using the SONAME as part of
> the translation domain?
Hm, interesting -- this could explain some weird problems I've had with
translated text on a machine where multiple versions are inst
Tom Lane wrote:
> Bruce Momjian writes:
> > When you do a pg_start_backup()/pg_stop_backup(), the *.backup files
> > created in pg_xlog are never deleted. Is that intended?
>
> Yes. See the documentation. DBAs can delete 'em if they feel like,
> but I don't see a strong argument for automatica
Bruce Momjian writes:
> When you do a pg_start_backup()/pg_stop_backup(), the *.backup files
> created in pg_xlog are never deleted. Is that intended?
Yes. See the documentation. DBAs can delete 'em if they feel like,
but I don't see a strong argument for automatically removing 'em.
They aren'
Bruce Momjian writes:
> Would someone comment on this bug report from February?
The report scored about zero out of zero IMHO: neither an actual report
of field trouble, nor a clear explanation of the supposed trouble, nor
a specific proposal what to do about it.
Without actual field trouble rep
When you do a pg_start_backup()/pg_stop_backup(), the *.backup files
created in pg_xlog are never deleted. Is that intended?
$ lf /u/pg/data/pg_xlog/
0001.0034C96C.backup00010004
0001.0034C9AC.backup00
After months of being behind, I have gone through my entire mailbox and
addressed all the patches held over from 8.0beta. I have loaded up the
patch queue and will apply them in a day or two.
http://momjian.postgresql.org/cgi-bin/pgpatches
Some of the patches lack documentation which I w
Bruce Momjian wrote:
> Can we get a list features we want for RESET CONNECTION? At this point,
> I see ideas but no consistent approach. Some say protocol only, others
> say an SQL command is fine, but the protocol has to find out it happened
> somehow. Is that a plan?
I have enhanced our TODO
Can we get a list features we want for RESET CONNECTION? At this point,
I see ideas but no consistent approach. Some say protocol only, others
say an SQL command is fine, but the protocol has to find out it happened
somehow. Is that a plan?
--
Bruce Momjian| http://c
Bruce Momjian wrote:
Tom Lane wrote:
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
No, I don't think so. It doesn't seem to be something that enough
people use to risk the change in behavior --- it might break something
that was working. But, if folks want it backported we can
Is this a direction we want to explore --- using the SONAME as part of
the translation domain?
---
Martin Pitt wrote:
-- Start of PGP signed section.
> Hi!
>
> Bruce Momjian [2005-02-09 18:05 -0500]:
> > > However, I just s
Markus Bertheau ☭ wrote:
Hmm, this gets really complicated and inconsistent. Complicated means
unusable. What about modifying the dimension syntax such that the second
number means number of elements instead of upper bound? That particular
problem would go away then, and array_upper('[0:0]={}'::i
Would someone comment on this bug report from February? I can confirm
the code is unchanged and is in function fe-connect.c::PQconnectPoll().
---
Florian Hars wrote:
>
> The following bug has been logged online:
>
> Bug r
I have waded through this email and the suggestion seems to be that on
Solaris we should add rpathdir based on the LD_RUN_PATH value at the
time of compile.
While this might be common on Solaris, I am not excited about
implementing it because it changes compile behavior based on an
environment va
Bruce Momjian wrote:
> John Hansen wrote:
> > ... Except,.. It was never decided if the 'C' locale
> optimisations was
> > going to be removed if/when implementing ICU.
>
> Uh, why would we remove it? Oh, meaning if the locale is C
> we bypass locale lookups? I think we will have to see what
On Tue, Jun 07, 2005 at 09:35:56AM +0900, a_ogawa wrote:
>
> Bruce Momjian wrote:
> > David Fetter wrote:
> > > On Mon, Jun 06, 2005 at 12:02:18PM -0400, Bruce Momjian wrote:
> > > >
> > > > Patch removed because we already have this functionality.
> > >
> > > We don't yet have this functionality,
On Mon, Jun 06, 2005 at 10:59:04PM +0300, Victor Y. Yegorov wrote:
> The question is: allocating pages this way is really ugly, I understand. Is
> there some API that would allow allocating N pages in the bulk way?
> Maybe this is a know problem, that has been already solved before?
> Any other id
Bruce Momjian wrote:
> David Fetter wrote:
> > On Mon, Jun 06, 2005 at 12:02:18PM -0400, Bruce Momjian wrote:
> > >
> > > Patch removed because we already have this functionality.
> >
> > We don't yet have this functionality, as the patch allows for using
> > second and later regex matches "()" in
John Hansen wrote:
> ... Except,.. It was never decided if the 'C' locale optimisations was
> going to be removed if/when implementing ICU.
Uh, why would we remove it? Oh, meaning if the locale is C we bypass
locale lookups? I think we will have to see what performance we have
with things.
> Th
... Except,.. It was never decided if the 'C' locale optimisations was
going to be removed if/when implementing ICU.
Tho I think the conclusion was a postgresql.conf parameter to
enable/disable the optimisations.
Either way, this code is now obsolete.
... John
> -Original Message-
> Fr
I think we have decided to use the ICU library to implement multiple locales.
---
John Hansen wrote:
> Hi list,
>
>
> Attached for your perusal, unicode versions of upper/lower, that work
> independent of locale except for
Yes,
Thank you! :)
.. John
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 07, 2005 10:07 AM
> To: John Hansen
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] unicode upper/lower functions
>
>
> I think we have decided to use the
I have added the unresolved issue referenced here to TODO:
http://archives.postgresql.org/pgsql-bugs/2005-01/msg00306.php
It relates to the use of rtree indexing:
* Fix incorrect rtree results due to wrong assumptions about "over"
operator semantics [rtree]
--
Bruce
Robert Treat wrote:
> On Monday 06 June 2005 17:35, Bruce Momjian wrote:
> > Josh Berkus wrote:
> > > Bruce,
> > >
> > > > I do like this idea. Can you make a general patch? Do others like the
> > > > idea of system tables showing error codes and keywords?
> > >
> > > Yes. However, I think the i
On Monday 06 June 2005 17:35, Bruce Momjian wrote:
> Josh Berkus wrote:
> > Bruce,
> >
> > > I do like this idea. Can you make a general patch? Do others like the
> > > idea of system tables showing error codes and keywords?
> >
> > Yes. However, I think the idea of additional system views has a
Christopher Kings-Lynne wrote:
What would be absolutely ideal is a reset connection command, plus some
way of knowing via the protocol if it's needed or not.
And a way of notifying the client that a reset has happened.
-O
---(end of broadcast)--
Josh Berkus wrote:
> Bruce,
>
> > I do like this idea. Can you make a general patch? Do others like the
> > idea of system tables showing error codes and keywords?
>
> Yes. However, I think the idea of additional system views has already been
> shot down in flames.
> Unless people think t
Bruce,
> I do like this idea. Can you make a general patch? Do others like the
> idea of system tables showing error codes and keywords?
Yes. However, I think the idea of additional system views has already been
shot down in flames.
Unless people think that it's reasonable to have a syste
I need your advice.
For on-disk bitmap I run a list of TIDs.
TIDs are stored in pages as an array, page's opaque data holds an array of
bits, indicating whether corresponding TID has been deleted and should be
skipped during the scan.
Pages, that contain TIDs list, are organized in extents, each
David Fetter wrote:
> On Mon, Jun 06, 2005 at 12:02:18PM -0400, Bruce Momjian wrote:
> >
> > Patch removed because we already have this functionality.
>
> We don't yet have this functionality, as the patch allows for using
> second and later regex matches "()" in the replacement pattern.
>
> The
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> On Mon, 6 Jun 2005, Tom Lane wrote:
>> Heikki Linnakangas <[EMAIL PROTECTED]> writes:
>>> Vacuum doesn't zero out the free space between lower and upper,
>>
>> It does now ;-)
> Oh :). Does it affect vacuum performance?
I haven't tried to measure
On Mon, 6 Jun 2005, Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
Vacuum doesn't zero out the free space between lower and upper,
It does now ;-)
Oh :). Does it affect vacuum performance?
How about adding a flag to XLogRecData to indicate if the space between
pd_lower and
Gevik babakhani wrote:
> Dear All,
>
>
>
> I am sure this is all asked before, so forgive me.
>
> Does anyone know (besides the documentation) if there is a graphical
> representation of the pg catalog?
Slide 65 in this presentation:
http://candle.pha.pa.us/main/writings/pgsql/intern
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Vacuum doesn't zero out the free space between lower and upper,
It does now ;-)
> How about adding a flag to XLogRecData to indicate if the space between
> pd_lower and pd_upper is meaningful or not? The XLogInsert caller probably
> knows that. T
Am Samstag, den 04.06.2005, 22:59 +0200 schrieb Gevik babakhani:
> Dear all,
>
>
>
> The PostgreSQL Developer Networkʼs Source Browser (beta1) is ready.
>
> If you got the time to check it for a moment, please do not hesitate
> to send your opinion.
Hm. wouldn't an install of trac/postgres
On Mon, 6 Jun 2005, Tom Lane wrote:
Junji TERAMOTO <[EMAIL PROTECTED]> writes:
In "whole buffer log", there is a page header that includes offset of
"hole" (lower and upper). If we use that information, we don't need
any overhead, do we?
No, because the WAL code cannot assume that all pages
В Пнд, 06/06/2005 в 08:58 -0700, Joe Conway пишет:
> Joe Conway wrote:
> > Actually, consistent with my last post, I think array_upper() on a
> > zero-element array should return NULL. A zero-element array has a
> > defined lower bound, but its upper bound is not zero -- it is really
> > undefin
On Mon, Jun 06, 2005 at 12:02:18PM -0400, Bruce Momjian wrote:
>
> Patch removed because we already have this functionality.
We don't yet have this functionality, as the patch allows for using
second and later regex matches "()" in the replacement pattern.
The function is misnamed. It should be
Joe Conway wrote:
Actually, consistent with my last post, I think array_upper() on a
zero-element array should return NULL. A zero-element array has a
defined lower bound, but its upper bound is not zero -- it is really
undefined.
Just to clarify my response, this is what I propose:
regressi
Markus Bertheau ☭ wrote:
В Пнд, 06/06/2005 в 10:44 -0400, Tom Lane пишет:
Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes:
By analogy, array_upper('{}'::TEXT[], 1) should return 0 instead of
NULL.
No, that doesn't follow ... we've traditionally considered '{}' to
denote a ze
Tom Lane wrote:
Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes:
By analogy, array_upper('{}'::TEXT[], 1) should return 0 instead of
NULL.
No, that doesn't follow ... we've traditionally considered '{}' to
denote a zero-dimensional array. A 1-D array of no elements is
'[1:0]
Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> >> No, I don't think so. It doesn't seem to be something that enough
> >> people use to risk the change in behavior --- it might break something
> >> that was working. But, if folks want it backported we can do it. It is
> >
Thanks!
Gevik babakhani wrote:
Regarding to update the techdocs and not reinveting the wheel, I am having a
mailng with Robert Treat of (webmaster pg) in order to see what can be
done.. any help is welcome... :)
Regards,
Gevik.
-Original Message-
From: Jonah H. Harris [mailto:[EMAIL
Regarding to update the techdocs and not reinveting the wheel, I am having a
mailng with Robert Treat of (webmaster pg) in order to see what can be
done.. any help is welcome... :)
Regards,
Gevik.
-Original Message-
From: Jonah H. Harris [mailto:[EMAIL PROTECTED]
Sent: Monday, June 06,
Is this really relevant to -hackers? I was thinking more along the lines
of -general.
Gevik babakhani wrote:
Dear All,
I am sure this is all asked before, so forgive me…
Does anyone know (besides the documentation) if there is a graphical
representation of the pg catalog?
Regards,
Gevik.
For this information, you can go through the code. I would suggest
reading through the catalog, heap access methods, storage manager, and
executor. Does anyone know of any good high-level docs on this?
Nithin Sontineni wrote:
Hi,
i want to know how create relation works and how
the pop
В Пнд, 06/06/2005 в 10:44 -0400, Tom Lane пишет:
> Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes:
> > By analogy, array_upper('{}'::TEXT[], 1) should return 0 instead of
> > NULL.
>
> No, that doesn't follow ... we've traditionally considered '{}' to
> denote a zero-dimensional
Dear All,
I am sure this is all asked before, so forgive me…
Does anyone know (besides the documentation) if there is a
graphical representation of the pg catalog?
Regards,
Gevik.
Gevik,
You still didn't answer my question as to why you're reinventing the
wheel. Why not just work on updating techdocs instead?
-Jonah
Tom Flavel wrote:
On 04/06/2005 22:59:19, Gevik babakhani wrote:
Dear all,
The PostgreSQL Developer Network's Source Browser (beta1) is ready.
I
I would suggest adding it to \ds or create a \ds+ so that it is in
common with the rest of the commands.
-Jonah
Gevik babakhani wrote:
So what would be your suggestion in order to add this functionality?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Markus Bertheau =?UTF-8?Q?=E2=98=AD?= <[EMAIL PROTECTED]> writes:
> By analogy, array_upper('{}'::TEXT[], 1) should return 0 instead of
> NULL.
No, that doesn't follow ... we've traditionally considered '{}' to
denote a zero-dimensional array. A 1-D array of no elements is
'[1:0]={}', just as Joe
On 6/6/05, Richard Huxton wrote:
> Jaime Casanova wrote:
> > I know you're right, but -when dealing with updateable views- doing
> > that implies to add a lot of time altering views when base table
> > change, and of course we maybe don't want all views get that values.
>
> Sorry for the late pos
Junji TERAMOTO <[EMAIL PROTECTED]> writes:
> In the XLogInsert(), it makes two kinds of logs, "whole buffer(page)
> log" and "partial buffer log", isn't it? Is it only "who buffer log"
> to generate a log with "hole"?
Right.
> Tom Lane wrote:
>> The overhead needed is only 2 bytes to show the nu
В Втр, 24/05/2005 в 00:06 -0400, Tom Lane пишет:
> Joe Conway <[EMAIL PROTECTED]> writes:
> > Markus Bertheau wrote:
> >> why does SELECT ARRAY(SELECT 1 WHERE FALSE) return NULL instead of
> >> ARRAY[] resp. '{}'?
>
> > Why would you expect an empty array instead of a NULL?
>
> I think he's got a
Jaime Casanova wrote:
I know you're right, but -when dealing with updateable views- doing
that implies to add a lot of time altering views when base table
change, and of course we maybe don't want all views get that values.
Sorry for the late posting on this thread.
Might there be any way to h
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 04 June 2005 16:46
> To: Mark Cave-Ayland (External)
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: Quick-and-dirty compression for WAL backup blocks
(cut)
> I've completed a test run for this (it's essentially M
On Wed, 2005-05-25 at 11:28 +1000, Neil Conway wrote:
> Tom Lane wrote:
> > Dunno. Depending on such a thing would require depending on a new flex
> > version, and seeing that the flex guys haven't put out a new release
> > since the badly broken 2.5.31 more than 2 years ago, I wouldn't hold
> > m
Hello all,
(B
(BI am interested in how to "Compress WAL entries".
(BThen, I study the source now, and read this discussion.
(B
(BThere are some questions.
(B
(B1.
(BIn the XLogInsert(), it makes two kinds of logs, "whole buffer(page)
(Blog" and "partial buffer log", isn't it? Is it only "
hey tom and others
look at these
how is the sum of all tables != database
qe18=# SELECT
pg_stat_get_db_blocks_fetched(771773788),pg_stat_get_db_blocks_hit(771773788);
pg_stat_get_db_blocks_fetched |
pg_stat_get_db_blocks_hit
---+--
63 matches
Mail list logo
