Hi,
My application is unable to connect to the postgresql database since the
database is throwing fallowing error:
Unspecified error: FATAL: 1 trigger record(s) not found for relation
"pg_shadow"
- PgOleDb; SQL= Error number: 80004005 FATAL: 1 trigger record(s) not found
for relation "pg_s
Hello,
I'd like to propose a new feature, Deadline-Based Vacuum Delay, the
syntax is something like "VACUUM IN 6 HOURS".
Vacuum is a non-trivial task to be performed. The database needs to be
vacuumed before the system performance suffers from the garbage; it also
needs to ensure the system won't
ITAGAKI Takahiro wrote:
Hello,
NTT staffs are working on TODO item:
| Create a bitmap of pages that need vacuuming
We call the bitmap "Dead Space Map" (DSM), that allows VACUUM to scan
only pages that need vacuuming or freezing. We'd like to discuss the
design on hackers and make agreements wit
Hello,
NTT staffs are working on TODO item:
| Create a bitmap of pages that need vacuuming
We call the bitmap "Dead Space Map" (DSM), that allows VACUUM to scan
only pages that need vacuuming or freezing. We'd like to discuss the
design on hackers and make agreements with community.
We implement
On Wed, Dec 27, 2006 at 02:49:41PM -0500, Tom Lane wrote:
> I've applied the attached patch to fix this, but not being much of a
> user of languages that have combining characters, I can't test it very
> well. Please check out the behavior and see if you like it.
Looks good so far. I've tested l
Roman Kononov wrote:
> On 12/27/2006 05:19 PM, Tom Lane wrote:
> > Roman Kononov <[EMAIL PROTECTED]> writes:
> >> On 12/27/2006 03:23 PM, Bruce Momjian wrote:
> >>> Are you sure? As I remember, computation automatically upgrades to
> >>> 'double'. See this program and output:
> >
> >> This is pl
Tom Lane wrote:
> Roman Kononov <[EMAIL PROTECTED]> writes:
> > On 12/27/2006 03:23 PM, Bruce Momjian wrote:
> >> Are you sure? As I remember, computation automatically upgrades to
> >> 'double'. See this program and output:
>
> > This is platform- and compiler- dependent:
>
> ... and probably
Tom Lane wrote:
> Roman Kononov <[EMAIL PROTECTED]> writes:
> > In float4mul() and float4div(), the computation should be double precision.
>
> Why? It's going to have to fit in a float4 eventually anyway.
One issue is in the patch comment:
!* Computations that slightly exceed FLOA
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > 566.973777
> > 327.158222 <- (1) write()
> > 560.773868 <- (2) sleep
> > 544.106645 <- (3) fsync()
>
> OK, so you are saying that performance dropped only during the write(),
> and not during the fsync()? Interesting.
Almost yes, but there is a smal
On Wed, Dec 27, 2006 at 06:11:55PM -0600, Andrew Dunstan wrote:
> Tom Lane wrote:
> > David Fetter <[EMAIL PROTECTED]> writes:
> >> On Wed, Dec 27, 2006 at 06:22:17PM -0500, Tom Lane wrote:
> >>> The problem with that is that "AS foo" already has a meaning, and it's
> >>> not this one.
> >
> >> How
Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
>> On Wed, Dec 27, 2006 at 06:22:17PM -0500, Tom Lane wrote:
>>> The problem with that is that "AS foo" already has a meaning, and it's
>>> not this one.
>
>> How about "AS (foo)" ?
>
> What if you want to specify an alias? This doesn't wo
On 12/27/2006 05:19 PM, Tom Lane wrote:
Roman Kononov <[EMAIL PROTECTED]> writes:
On 12/27/2006 03:23 PM, Bruce Momjian wrote:
Are you sure? As I remember, computation automatically upgrades to
'double'. See this program and output:
This is platform- and compiler- dependent:
... and prob
On Wed, Dec 27, 2006 at 06:36:56PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Wed, Dec 27, 2006 at 06:22:17PM -0500, Tom Lane wrote:
> >> The problem with that is that "AS foo" already has a meaning, and it's
> >> not this one.
>
> > How about "AS (foo)" ?
>
> What i
David Fetter <[EMAIL PROTECTED]> writes:
> On Wed, Dec 27, 2006 at 06:22:17PM -0500, Tom Lane wrote:
>> The problem with that is that "AS foo" already has a meaning, and it's
>> not this one.
> How about "AS (foo)" ?
What if you want to specify an alias? This doesn't work:
FROM myverylo
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> OK, I guess my only other question is to do with recursive/hierarchical
> queries: How will we handle those? All in same context?
Offhand I don't think it matters. Recursive queries are recursive in
the data, not in the plan tree.
Roman Kononov <[EMAIL PROTECTED]> writes:
> In float4mul() and float4div(), the computation should be double precision.
Why? It's going to have to fit in a float4 eventually anyway.
regards, tom lane
---(end of broadcast)--
On Wed, Dec 27, 2006 at 06:22:17PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > What would be involved in fixing the casting operation so that the
> > following would work?
>
> > CREATE TYPE foo AS (
> > a INT4,
> > b INT8,
> > c POINT,
> > d TEXT
> > );
>
David Fetter <[EMAIL PROTECTED]> writes:
> What would be involved in fixing the casting operation so that the
> following would work?
> CREATE TYPE foo AS (
> a INT4,
> b INT8,
> c POINT,
> d TEXT
> );
> CREATE FUNCTION bar(output_type TEXT)
> RETURNS SETOF RECORD
> ...
> SELECT
Roman Kononov <[EMAIL PROTECTED]> writes:
> On 12/27/2006 03:23 PM, Bruce Momjian wrote:
>> Are you sure? As I remember, computation automatically upgrades to
>> 'double'. See this program and output:
> This is platform- and compiler- dependent:
... and probably irrelevant, too. We should stor
Stephen Frost <[EMAIL PROTECTED]> writes:
> While a wildcard does make sense (ie: www*.postgresql.org), I would
> generally expect 'commandprompt.com' to mean '*.commandprompt.com'
> implicitly.
No, that would be a really bad idea. It's not unlikely that
commandprompt.com refers to a specific hos
On Wed, 2006-12-27 at 18:05 -0500, Tom Lane wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > Is it possible to allocate the subquery in a child context of the main
> > query, so that it is technically a different context, yet can be freed
> > simultaneously?
>
> That's exactly what the code
Bruce Momjian <[EMAIL PROTECTED]> writes:
> David Fetter wrote:
>> Is anybody claiming this TODO? Is the design fleshed out enough for
>> someone to go forward with it?
> I think we just need to decide on the user API for this.
... and the catalog representation.
regards
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Is it possible to allocate the subquery in a child context of the main
> query, so that it is technically a different context, yet can be freed
> simultaneously?
That's exactly what the code *was* doing, but the problem is that we'd
free the child contex
On Wed, 2006-12-27 at 23:26 +0100, Martijn van Oosterhout wrote:
> On Wed, Dec 27, 2006 at 09:24:06PM +, Simon Riggs wrote:
> > On Fri, 2006-12-22 at 13:53 -0500, Bruce Momjian wrote:
> >
> > > I assume other kernels have similar I/O smoothing, so that data sent to
> > > the kernel via write()
Stephen Frost wrote:
* Andrew Dunstan ([EMAIL PROTECTED]) wrote:
Before we rehearse the discussion we had in June again, please review
it. It ended on these sensible words from Tom at
http://archives.postgresql.org/pgsql-hackers/2006-02/msg00550.php :
I'd have to disagree with this se
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I think what we should probably consider is removing CheckFloat4Val
>> and CheckFloat8Val altogether, and just letting the float arithmetic
>> have its head. Most modern hardware gets float arithmetic right per
>> spec, and we shouldn'
On Wed, Dec 27, 2006 at 09:24:06PM +, Simon Riggs wrote:
> On Fri, 2006-12-22 at 13:53 -0500, Bruce Momjian wrote:
>
> > I assume other kernels have similar I/O smoothing, so that data sent to
> > the kernel via write() gets to disk within 30 seconds.
> >
> > I assume write() is not our che
* Andrew Dunstan ([EMAIL PROTECTED]) wrote:
> Before we rehearse the discussion we had in June again, please review
> it. It ended on these sensible words from Tom at
> http://archives.postgresql.org/pgsql-hackers/2006-02/msg00550.php :
I'd have to disagree with this sentiment and agree with Gre
Joshua D. Drake wrote:
Hello,
Per the TODO list:
Allow pg_hba.conf to specify host names along with IP addresses
Host name lookup could occur when the postmaster reads the pg_hba.conf
file, or when the backend starts. Another solution would be to reverse
lookup the connection IP and check th
On Wed, 2006-12-27 at 17:02 -0500, Stephen Frost wrote:
> * Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> > On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote:
> > > I'm inclined towards doing the reverse-DNS of the connecting IP and then
> > > checking that the forward of that matches.
> >
> >
On Dec 27, 2006, at 1:47 PM, Joshua D. Drake wrote:
On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote:
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
Allow pg_hba.conf to specify host names along with IP addresses
Excellent.
Host name lookup could occur when the postmaster reads the
p
On Mon, 2006-12-18 at 14:47 +0900, Takayuki Tsunakawa wrote:
> Hello, Itagaki-san, all
>
> Sorry for my long mail. I've had trouble in sending this mail because
> it's too long for pgsql-hackers to accept (I couldn't find how large
> mail is accepted.) So I'm trying to send several times.
> Ple
David Fetter wrote:
> On Fri, Sep 29, 2006 at 11:55:18PM -0400, Bruce Momjian wrote:
> >
> > Added to TODO:
> >
> > * Allow more complex user/database default GUC settings
> >
> > Currently, ALTER USER and ALTER DATABASE support per-user and
> > per-database defaults. Consid
Folks,
While using DBI-Link, I've noticed a little lacuna in how functions
returning (SETOF) RECORD work, namely, that you have to cast them to
explicit lists of columns, even when that list of columns corresponds
to an existing complex type.
What would be involved in fixing the casting operation
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote:
> > I'm inclined towards doing the reverse-DNS of the connecting IP and then
> > checking that the forward of that matches.
>
> Hmm what if it doesn't? Which is the case any many scenario. My tho
>>> Host name lookup could occur when the postmaster reads the pg_hba.conf
>>> file, or when the backend starts. Another solution would be to reverse
>>> lookup the connection IP and check that hostname against the host names
>>> in pg_hba.conf. We could also then check that the host name maps to t
On Fri, 2006-12-22 at 13:53 -0500, Bruce Momjian wrote:
> I assume other kernels have similar I/O smoothing, so that data sent to
> the kernel via write() gets to disk within 30 seconds.
>
> I assume write() is not our checkpoint performance problem, but the
> transfer to disk via fsync().
W
On Tue, 2006-12-26 at 10:34 -0500, Doug Knight wrote:
> I'm new to the forums, so bear with me on my questions. I've set up an
> auto-archive and auto-recover pair of databases using pg_standby,
> which I'm prototyping various products for high availability.
Thanks for the feedback. pg_standby w
On Tue, 2006-12-26 at 10:47 -0500, Tom Lane wrote:
> As you can probably guess, I'm leaning to #3, but wanted to see if
> anyone had an objection or a better idea.
Is it possible to allocate the subquery in a child context of the main
query, so that it is technically a different context, yet can b
On Wed, 2006-12-27 at 22:16 +1100, Gavin Sherry wrote:
> > But actually I'm not convinced we need to worry about efficient storage
> > of small bitmaps at all. The typical use case for bitmap indexes is
> > large tables with small number of distinct values, and the problem
> > doesn't really arise
On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote:
> * Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> > Allow pg_hba.conf to specify host names along with IP addresses
>
> Excellent.
>
> > Host name lookup could occur when the postmaster reads the pg_hba.conf
> > file, or when the backend sta
> I get 'inf'. I am on BSD and just tested it on Fedora Core 2 and got
> 'inf' too.
Ubuntu Edgy 64bit on Athlon 64X2 returns inf.
Joshua D. Drake
>
> > A slightly less radical proposal is to reject only the case where
> > isinf(result) and neither input isinf(); and perhaps likewise with
> >
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
> Allow pg_hba.conf to specify host names along with IP addresses
Excellent.
> Host name lookup could occur when the postmaster reads the pg_hba.conf
> file, or when the backend starts. Another solution would be to reverse
> lookup the connection IP a
On Fri, Sep 29, 2006 at 11:55:18PM -0400, Bruce Momjian wrote:
>
> Added to TODO:
>
> * Allow more complex user/database default GUC settings
>
> Currently, ALTER USER and ALTER DATABASE support per-user and
> per-database defaults. Consider adding per-user-and-datab
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have made some more progress on this patch.
>
> I'm not convinced that you're fixing things so much as doing your best
> to destroy IEEE-compliant float arithmetic behavior.
>
> I think what we should probably consider is removing
Hello,
Per the TODO list:
Allow pg_hba.conf to specify host names along with IP addresses
Host name lookup could occur when the postmaster reads the pg_hba.conf
file, or when the backend starts. Another solution would be to reverse
lookup the connection IP and check that hostname against the ho
On Wed, Dec 27, 2006 at 03:42:36PM +, Heikki Linnakangas wrote:
> >I wonder what would happen if somebody implemented automatic index
> >exclusion conditions after use of an INDEX proved to be in the realm
> >of the worst case scenario? :-)
> I'm sorry, I don't understand that sentence...
I wa
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Dhanaraj M wrote:
>> I am sending the patch for the following TODO item:
>> Allow the identifier length to be increased via a configure option
> You should use pg_config.h, not mangle postgres_ext.h like that. Or
> maybe generate postgres_ext.h from an
I wrote:
> Actually, looking at the comments for ucs_wcwidth() in wchar.c, it seems
> that this is already accounted for in the "dsplen" output: characters
> for which -1 is returned are control characters, characters for which
> 0 is returned should be printed as-is and counted as zero width. So
I notice that the latest pgindent run has decided that comments attached
to "else" should be moved onto the next line, as in this example in
src/bin/psql/mbprint.c:
{
linewidth += 4;
format_size += 4;
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have made some more progress on this patch.
I'm not convinced that you're fixing things so much as doing your best
to destroy IEEE-compliant float arithmetic behavior.
I think what we should probably consider is removing CheckFloat4Val
and CheckFloat8
Thanks a lot, it worked:) Actually, I have tried to include "postgres.h"
before, but not at the top of the other includes.
regards,
dakotali
Bruce Momjian <[EMAIL PROTECTED]> wrote:
Ah, all *.c files must have this at the top before they include _any_
other files, including system include file
dakotali kasap wrote:
my_writer.c looks like:
-
#include "nodes/nodes.h"
#include
#include "nodes/pg_list.h"
well, you normally have to include "postgres.h" before any other
postgres header.
cheers
andrew
---(end o
Ah, all *.c files must have this at the top before they include _any_
other files, including system include files:
#include "postgres.h"
You will see that all our backend files follow this rule.
---
dakotali kasap
dakotali kasap wrote:
Hi,
I have one source and one header file which are called my_writer.h and
my_writer.c. I included my_writer.h inside postgres.c and do the
implementation of declared functions inside my_writer.c. When I
include, some other header files of postgresql (like nodes/pg_list.
Sorry I did not want to bother you with the details, I just thought that there
is smth that I have to do apart from adding the object file name into the
Makefile.
So, here is the whole picture:
I want to write a function that takes the raw parsetree and rewrites it
according to my rules, then
Hi,
I have one source and one header file which are called my_writer.h and
my_writer.c. I included my_writer.h inside postgres.c and do the implementation
of declared functions inside my_writer.c. When I include, some other header
files of postgresql (like nodes/pg_list.h or nodes/nodes.h) in m
dakotali kasap wrote:
> Hi,
>
> I want to add my .c and .h source files into the postgresql project.
> What kind of changes should I make with the Makefiles. It seems that,
> it is not enough just to add the object file of the C files into the
> Makefile.
Huh, why not? Typically you just add the
Hi,
I want to add my .c and .h source files into the postgresql project. What kind
of changes should I make with the Makefiles. It seems that, it is not enough
just to add the object file of the C files into the Makefile.
Can anyone help to me please?
kind regards,
dakotali
___
[EMAIL PROTECTED] wrote:
On Wed, Dec 27, 2006 at 10:16:54PM +1100, Gavin Sherry wrote:
On Wed, 27 Dec 2006, Heikki Linnakangas wrote:
But actually I'm not convinced we need to worry about efficient storage
of small bitmaps at all. The typical use case for bitmap indexes is
large tables with sma
Joshua D. Drake wrote:
>
> > The current terminology of live and dead is already used in many places in
> > the
> > documentation and in userspace; mostly around the need for maintainance of
> > dead tuples within tables, reindex cleaning up dead pages, and even in the
> > vacuum commands outp
On Wed, Dec 27, 2006 at 10:16:54PM +1100, Gavin Sherry wrote:
> On Wed, 27 Dec 2006, Heikki Linnakangas wrote:
> > But actually I'm not convinced we need to worry about efficient storage
> > of small bitmaps at all. The typical use case for bitmap indexes is
> > large tables with small number of di
On Wed, 27 Dec 2006, Heikki Linnakangas wrote:
> Jie Zhang wrote:
> > The "bitmap data segment" sounds good in terms of space. The problem is that
> > one bitmap is likely to occupy more pages than before, which may hurt the
> > query performance.
>
> We could have segments of say 1/5 of page. Whe
On Wed, 27 Dec 2006, Heikki Linnakangas wrote:
> Gavin Sherry wrote:
> > On Tue, 26 Dec 2006, Heikki Linnakangas wrote:
> >> for typical bitmap index use cases and most of the needed pages should
> >> stay in memory, but could we simplify this? Why do we need the auxiliary
> >> heap, couldn't we j
Jie Zhang wrote:
The "bitmap data segment" sounds good in terms of space. The problem is that
one bitmap is likely to occupy more pages than before, which may hurt the
query performance.
We could have segments of say 1/5 of page. When a bitmap grows larger
than that, the bitmap would be moved
Gavin Sherry wrote:
On Tue, 26 Dec 2006, Heikki Linnakangas wrote:
for typical bitmap index use cases and most of the needed pages should
stay in memory, but could we simplify this? Why do we need the auxiliary
heap, couldn't we just store the blk+offset of the LOV item directly in
the b-tree in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Dec 27, 2006 at 09:39:22AM +0100, Benny Amorsen wrote:
> > "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> TL> Anyone against making it case-insensitive, speak now or hold your
> TL> peace.
>
> SI-units are inherently case-sensitive [...
>> And instead of having separate LOV pages that store a number of LOV
>> items, how about storing each LOV item on a page of it's own, and using
>> the rest of the page to store the last chunk of the bitmap. That would
>> eliminate one page access, but more importantly, maybe we could then get
>>
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> Anyone against making it case-insensitive, speak now or hold your
TL> peace.
SI-units are inherently case-sensitive. The obvious example is that
now you will allow people to specify an amount in millibytes, while
interpreting it in megabytes.
69 matches
Mail list logo
