> > How subselects run queries again and again?
>
> They don't end and restart them; they just rescan them. If we had
Thanks for recollection.
> this substitute-a-new-tuple hack integrated into the Param mechanism,
> then EvalPlanQual could use ExecReScan too, but at the moment no...
I see.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I know Tom has talked about doing schemas for 7.2. I have an idea.
> I did temp tables by doing the temp table mapping as part of cache
> lookups. Though this seems like a strange idea, the cache is the
> central location for name/tuple lookups, and is
On Tue, 15 May 2001, Gavin Sherry wrote:
> Hi all,
>
> Can't for the life of me figure out the problem here:
>
> CREATE TABLE "b" (
> "id" bigint,
> "string" text
> );
>
> CREATE INDEX "b_pkey" on "b" using btree ( "id" "int8_ops" );
Because of a problem with the typing of i
Gavin Sherry <[EMAIL PROTECTED]> writes:
> CREATE TABLE "b" (
> "id" bigint,
> "string" text
> );
> SELECT * FROM b WHERE id=1;
Try "WHERE id = 1::bigint".
(Hey Bruce, is there anything about this in the FAQ?)
regards, tom lane
-
Forgot to add that naturally, I have VACUUM ANALYZE'd.
Gavin
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the m
"Vadim Mikheev" <[EMAIL PROTECTED]> writes:
>> However, EvalPlanQual still leaks more memory than suits me ---
>> auxiliary memory allocated by the plan nodes is not recovered.
> Isn't plan shutdown supposed to free memory?
Yeah, but it leaks all over the place; none of the plan node types
bothe
On Mon, 14 May 2001, Tom Lane wrote:
> Philip Warner <[EMAIL PROTECTED]> writes:
> > It is worth considering skipping the entire 'copy to children' approach?
> > Something like:
> > pg_constraints(constraint_id, constraint_name, constraint_details)
> > pg_relation_constraints(rel_id, constrai
> However, EvalPlanQual still leaks more memory than suits me ---
> auxiliary memory allocated by the plan nodes is not recovered.
> I think the correct way to implement it would be to create a new
> memory context for each level of EvalPlanQual execution and use
> that context as the "per-query c
Hi all,
Can't for the life of me figure out the problem here:
CREATE TABLE "b" (
"id" bigint,
"string" text
);
CREATE INDEX "b_pkey" on "b" using btree ( "id" "int8_ops" );
Given 2000 tuples in b, vacuum verbose analyze:
test=# vacuum verbose analyze b;
NOTICE: --Relation b-
At 23:34 14/05/01 -0400, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> writes:
>> It is worth considering skipping the entire 'copy to children' approach?
>> Something like:
>> pg_constraints(constraint_id, constraint_name, constraint_details)
>> pg_relation_constraints(rel_id, constraint
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Actually this brings up a problem I'm having with ALTER TABLE ADD
> CONSTRAINT and since it mostly affects you with DROP CONSTRAINT, I'll
> bring it up here. If you have a table that has check constraints or
> is inherited from multiple tables, what's
At 19:50 14/05/01 -0700, Stephan Szabo wrote:
>
>If it's $2 in the parent,
>but the child already has a $2 defined, what should be done? The
>reason this affects drop constraint is knowing what to drop in the
>child. If you drop $2 on the parent, what constraint(s) on the child
>get dropped?
>
Philip Warner <[EMAIL PROTECTED]> writes:
> It is worth considering skipping the entire 'copy to children' approach?
> Something like:
> pg_constraints(constraint_id, constraint_name, constraint_details)
> pg_relation_constraints(rel_id, constraint_id)
> Then, when we drop constraint 'FRED', t
At 19:50 14/05/01 -0700, Stephan Szabo wrote:
>
>If it's $2 in the parent,
>but the child already has a $2 defined, what should be done? The
>reason this affects drop constraint is knowing what to drop in the
>child. If you drop $2 on the parent, what constraint(s) on the child
>get dropped?
AF
On Tue, 15 May 2001, Christopher Kings-Lynne wrote:
> Lastly, inheritance? I plan to leave out worrying about inheritance for
> starters, especially since it seems that half the constraints when added
> don't even propagate themselves properly to child tables...
Actually this brings up a proble
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I can easily have pg_index.indisclustered updated to 'true' if you ever
> CLUSTER the index. Is that useful to anyone? Remember, clustering
> doesn't remain if you modify the table.
I don't see any value in it as long as CLUSTER is in the disreputable
I wrote:
> The direct cause of the problem is that EvalPlanQual isn't completely
> initializing the estate that it sets up for re-evaluating the plan.
> In particular it's not filling in es_result_relations and
> es_num_result_relations, which need to be set up if the top plan node
> is an Append.
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> AFAIK this is a working feature, and I am going to insist that you
>> keep your hands off it ...
> Really, it actually works? What are they?
Read create_indexscan_plan().
regards, tom lane
---(end of
"G. Anthony Reina" <[EMAIL PROTECTED]> writes:
> which is how it looks to be used in async.c. I simply added a specific
> type-cast:
> notifyName = (char *) strdup(relname);
That absolutely should NOT be necessary; there should be a proper
extern declaration of strdup visible. Perhaps it should
"G. Anthony Reina" <[EMAIL PROTECTED]> writes:
> There's a new problem with async.c:
> cc-1515 cc: ERROR File = async.c, Line = 172
> A value of type "int" cannot be assigned to an entity of type "char
> *".
> notifyName = strdup(relname);
>^
Eviden
Tom Lane wrote:
> > #if _XOPEN4UX || defined(_BSD_TYPES) || defined(_BSD_COMPAT)
>
> Next thought is that maybe none of these control symbols are defined
> by default --- could you look into that possibility? Perhaps some
> compiler switches or #defines are needed to get IRIX to allow
> "struct
Tom Lane wrote:
> Evidently IRIX also considers strdup() to be nonstandard :-(
>
> It's hard to believe that SGI is quite this braindead. I think there is
> something broken about configure on your setup. Can't tell what from
> here --- suggest you call in some IRIX gurus.
>
Yep. So goes SGI.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is lossy and partial indexes the same?
No.
> I can't see how they were
> supposed to be used. The _only_ mention of this field I see in
> indexcmd.c, around line 132.
You missed a few then --- the most critical being in createplan.c.
AFAIK this is a
Hi, got an error while sending this..so resending.
> Hi,
> l see that a lot of people have the same problem and have posted questions
> but I couldn't find an answer on the web.
>
> I have Postgresql 6.5.3 running on Debian Linux.
> And I use the iODBC driver manager 2.50.3 to make the ODBC cal
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Should I remove this column?
NO. The fact that we don't currently have any lossy index types doesn't
mean that we won't ever have them again. I've been wondering, for
example, whether the frequently heard requests for case-insensitive
indexes might no
"G. Anthony Reina" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Hm. Which system header file defines struct timeval on IRIX?
>> I'd expect or , but maybe they keep it
>> someplace unusual.
> In /usr/include/sys/time.h:
> #if _XOPEN4UX || defined(_BSD_TYPES) || defined(_BSD_COMPAT)
Next th
Patrick Welche <[EMAIL PROTECTED]> writes:
> On Sat, May 12, 2001 at 08:00:42PM -0400, Tom Lane wrote:
>> There is a BSD-license gettext clone project, but it doesn't look to be
>> very far along.
> What's missing with it?
Where did you find an actual release meant for public consumption?
I had
On Mon, 14 May 2001, Bruce Momjian wrote:
> > Bruce Momjian wrote:
> > >
> > > Can someone tell me what we use indislossy for?
> >
> > IIRC it means that if you get something by this index you must check
> > again in the actual data
> >
> > I think that at least the GIST intarray (actually intset
> Hi,
>
> l see that a lot of people have the same problem and have posted questions
> but I couldn't find an answer on the web.
>
> I have Postgresql 6.5.3 running on Debian Linux.
> And I use the iODBC driver manager 2.50.3 to make the ODBC calls.
>
> Am not able to insert data into Postgres
On Mon, May 14, 2001 at 09:36:56PM +0200, Peter Eisentraut wrote:
> Patrick Welche writes:
>
> > > I have no objection to the gettext API, but I was and still am concerned
> > > about depending on GNU gettext's code, because of license conflicts.
> > > There is a BSD-license gettext clone project
On Sun, 29 Apr 2001 20:04:19 + (UTC), [EMAIL PROTECTED]
(Bruce Momjian) wrote:
>Here is a general call for people to review other open-source database
>software and report back on things PostgreSQL can learn from them.
>
>I can see Interbase, MySQL, and SAP DB as being three database that
>wo
Seems little point in posting this to postgresql groups . . .preaching to
the converted??? Perhaps you should post on a micro$oft or a general SQL
group?
Oh, and how about a good guide for upsizing from M$ SQL and / or M$ ACCESS
to Postgresql - that'd be far more usefull ...
(Aside: Money is not
On Sat, May 12, 2001 at 08:00:42PM -0400, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > * Translation: If we want to use gettext I can get started. I don't
> > think I'm interested in using any other interface.
>
> I have no objection to the gettext API, but I was and sti
Tom Lane wrote:
> "G. Anthony Reina" <[EMAIL PROTECTED]> writes:
> >> In postgres_ext.h, I changed:
> >>
> >> #define NAMEDATALEN 32
> >> to
> >> #define NAMEDATALEN 51
> >>
> >> Everything compiled and installed. However, the initdb started up but
> >> then just said that it failed.
>
> I have n
Tom Lane wrote:
> > cc-1070 cc: ERROR File = xact.c, Line = 696
> > The indicated type is incomplete.
>
> > struct timeval delay;
> >^
>
> Hm. Which system header file defines struct timeval on IRIX?
> I'd expect or , but maybe t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I think so. I have heard no 7.1.2 date discussion yet.
Soon, I hope --- but we have a nasty EvalPlanQual bug to fix also,
so it's not going to be today ;-)
regards, tom lane
---(end of broadcast)---
Jan Wieck <[EMAIL PROTECTED]> writes:
> The detail I'm wondering about most is how you'd know in an
> UPDATE case which two tuples (one deleted during this XACT
> and one inserted) are the two for OLD and NEW in the call to
> the trigger.
Ugh ... good point. There's no back
Franck Martin <[EMAIL PROTECTED]> writes:
> The uuidgen program creates a new universally unique identifier (UUID)
> using the libuuid(3)
>library. The new UUID can reasonably be considered unique among all
> UUIDs created on the
>local system, and among UUIDs created on othe
Kovacs Zoltan <[EMAIL PROTECTED]> writes:
> If the WHERE clause doesn't contain any input parameters (i.e. $1), I
> don't get into any trouble.
Is this the known bug with failure if the SELECT returns zero rows?
regards, tom lane
---(end of broadc
Kovacs Zoltan <[EMAIL PROTECTED]> writes:
> In 7.1.1 the following statement doesn't work (backend closes
> immediately):
> SELECT INTO var1, var2 col1, col2 FROM table WHERE conditions;
Would you mind providing a complete test case, so that we don't waste
time guessing at context?
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> What do I use instead of the CatalogIndexInsert command to tell the index
> that a tuple has been removed?
Nothing. The tuple isn't really gone, and neither are its index
entries. Getting rid of them later is VACUUM's problem.
BTW, there
On Sat, May 12, 2001 at 11:21:44PM +0200, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > Peter E. had implied that he wanted to tackle the elog issues for 7.2,
> > but I'm not sure if he's committed to it or not.
>
> Well...
>
> * Automatically add filename, line, function name: Easy to code
42 matches
Mail list logo