Hello all.
Is there a way to directly access PGSQL from a Javascript application?
With no application server intervention, I mean.
Just like libq allows access from C/C++.
--
Fahrbahn ist ein graues Band
weisse Streifen, grüner Rand
--
Sent via pgsql-general mailing list
to the DB, is this favourable?
Allan.
On Fri, Jan 30, 2009 at 1:40 PM, Reg Me Please regmeple...@gmail.com
wrote:
Hello all.
Is there a way to directly access PGSQL from a Javascript application?
With no application server intervention, I mean.
Just like libq allows access from C/C
I already have a JS interpreter (spidermonkey) but there is no PGSQL
interfacing API!
This'd be why I'm asking.
On Friday 30 January 2009 13:24:59 Sean Davis wrote:
On Fri, Jan 30, 2009 at 7:09 AM, Reg Me Please regmeple...@gmail.comwrote:
I'd like to write part of the application
On Friday 30 January 2009 14:26:45 Peter Eisentraut wrote:
Gregory Stark wrote:
So, what do people say? Is Postgres perfect in your world or does it do
some things which rub you the wrong way?
* No offer of anything-but-CVS on pgfoundry.org
* Lack of REINDEX CONCURRENTLY
* Too many
On Thursday 22 January 2009 09:36:53 Kent Tong wrote:
Hi,
I am running a Chinese edition of XP. When I start psql, it is probably
trying to display Chinese and
maybe it gets the encoding wrong, it displays garbage in its console. Is
there any way to tell it to
just use English instead? In
On Thursday 22 January 2009 10:04:58 Kent Tong wrote:
Reg Me Please wrote:
psql --help ?
which option you're referring to? I tried --locale but it had no effect.
-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available
On Thursday 22 January 2009 10:51:41 Kent Tong wrote:
Reg Me Please wrote:
Weel, you have two locales: one on the client and one the server.
The former is needed for translations to the server whenver the two
don't
match.
The latter is chosen at the CREATE DATABASE dbname ENCODING
On Thursday 22 January 2009 18:57:16 Osvaldo Kussama wrote:
2009/1/22, Adrian Klaver akla...@comcast.net:
On Thursday 22 January 2009 8:16:46 am Alvaro Herrera wrote:
Grzegorz Jaśkiewicz escribió:
test2=# insert into dupa(a) select 'current_timestamp' from
generate_series(1,100);
On Monday 19 January 2009 23:28:08 Reg Me Please wrote:
On Monday 19 January 2009 22:49:17 Gerhard Heift wrote:
On Mon, Jan 19, 2009 at 08:19:06PM +0100, Reg Me Please wrote:
Hi all.
I have a maintenance PL/pgSQL function that needs to recreate a partial
index (not a REINDEX, though
Hi all.
I have a maintenance PL/pgSQL function that needs to recreate a partial index
(not a REINDEX, though).
In the WHERE condition of the index I have one of the function arguments.
A plain CREATE INDEX ... WHERE ... will lead to a runtime error like this:
tmp2=# SELECT * FROM f_maint1(
On Monday 19 January 2009 22:49:17 Gerhard Heift wrote:
On Mon, Jan 19, 2009 at 08:19:06PM +0100, Reg Me Please wrote:
Hi all.
I have a maintenance PL/pgSQL function that needs to recreate a partial
index (not a REINDEX, though).
In the WHERE condition of the index I have one
While I do understand that the BETWEEN operator is actually synctactic
sugar, from time to time I find myself wondering about a better BETWEEN for
DATEs, TIMEs and TIMESTAMPs (but not only these ones).
Infact I always have managed ranges where the lower part is to be matched with
the =
On Wednesday 14 January 2009 11:46:11 Louis-David Mitterrand wrote:
Hi,
This works:
critik=# select current_timestamp::abstime::int4 as score order by
score;
This doesn't:
critik=# select current_timestamp::abstime::int4 as score order by
score +
1; ERROR: column score
On Wednesday 14 January 2009 22:38:07 Jeff Davis wrote:
On Wed, 2009-01-14 at 13:35 -0800, Jeff Davis wrote:
I think the best solution is to make first-class interval types (for
time as well as other types). Those intervals can then have operators
like contains and contained by which would
On Wednesday 14 January 2009 22:38:07 Jeff Davis wrote:
On Wed, 2009-01-14 at 13:35 -0800, Jeff Davis wrote:
I think the best solution is to make first-class interval types (for
time as well as other types). Those intervals can then have operators
like contains and contained by which would
On Tuesday 13 January 2009 21:56:56 Mohamed wrote:
Hi. How would I return the number of matches found by a query, but when I
only want to return 30 of them ?
In MySQL there is a way of calling SQL_CALC_FOUND_ROWS to do this?
Is there something similiar that can be done in PostgreSQL ? Do I
On Monday 12 January 2009 09:40:22 Phoenix Kiula wrote:
2009/1/12 Thomas Markus t.mar...@proventis.net:
Thanks. But it used to work without this, and more importantly, this
doesn't explain why the queries are so exceedingly slow now! Any
thoughts?
When queries used to be fast and now are
On Monday 12 January 2009 10:18:59 Phoenix Kiula wrote:
When queries used to be fast and now are slow very often depends upon the
indexes. Less frequently upon the amount of memory available for cache
and the server configuration.
Do you used ti have any index on that column?
Do you have
On Monday 12 January 2009 21:38:02 Bruno Lavoie wrote:
Hello,
I have a column with a small number of distinct values, indexing this
one with a standard BTree is useless. How do I can index this column
efficiently? I searched and it seems that pg doesn't support the
creation of persistent
On Friday 09 January 2009 15:46:51 Jeremiah Jahn wrote:
On Fri, 2009-01-09 at 08:17 +0100, Reg Me Please wrote:
On Friday 09 January 2009 00:10:53 Jeremiah Jahn wrote:
Just wanted to say thank you for version 8.3.
The ordered indexing has dropped some of my search times from over 30
Hi.
For an INNER JOINed query, EXPLAIN says that a nested loop is responsible
for the big part of the time needed to run.
The 2 tables JOINed are:
T1: multi-million rows
T2: few dozens rows
The join is though a single column in both sides and it's NOT a PK in either
table. But I have indexes
=8
width=8)
Index Cond: ((T1.prod_id = 42) AND (T1.fk1 = T2.fk1))
On Friday 09 January 2009 19:22:28 Victor Nawothnig wrote:
Could you provide the output of EXPLAIN ANALYZE with your query?
On Fri, Jan 9, 2009 at 7:06 PM, Reg Me Please regmeple...@gmail.com wrote:
Hi
On Friday 09 January 2009 20:00:36 Thomas Pundt wrote:
Reg Me Please wrote:
Here it comes:
Aggregate (cost=227.59..227.61 rows=1 width=8)
- Nested Loop (cost=0.00..227.34 rows=49 width=8)
- Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
Filter: (fld1
On Friday 09 January 2009 20:00:57 Tom Lane wrote:
Reg Me Please regmeple...@gmail.com writes:
Aggregate (cost=227.59..227.61 rows=1 width=8)
- Nested Loop (cost=0.00..227.34 rows=49 width=8)
- Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
Filter: (fld1
:
No. there are no name clashes.
I actually changed the names in posted text a bit. The arguments,
declared variables and column names, all have their unique prefixes.
Thanks
Mayuresh
Reg Me Please wrote:
IS there any name clash with a function argument?
--
Fahrbahn ist ein graues Band
Maybe I'm missing the point, but have read about quote_ident() and
quote_literal() at chapter 9.4 String Functions and Operators?
BR
--
Fahrbahn ist ein graues Band
weisse Streifen, grüner Rand
On Thursday 08 January 2009 09:52:29 Mohamed wrote:
. any one?
On Wed, Jan 7, 2009 at 8:07
On Friday 09 January 2009 00:10:53 Jeremiah Jahn wrote:
Just wanted to say thank you for version 8.3.
The ordered indexing has dropped some of my search times from over 30
seconds to 3. I've been beating my head against this issue for over 8
years. I will drink to you tonight.
thanx again,
IS there any name clash with a function argument?
--
Fahrbahn ist ein graues Band
weisse Streifen, grüner Rand
On Thursday 08 January 2009 08:30:07 Mayuresh Nirhali wrote:
Hello,
I am working with 8.1.4 pgsql as my database backend. I have a function
written in plpgsql language, that queries
You need to write a process that will do it.
At best you can use crontab if your a lucky and use Unix.
--
Fahrbahn ist ein graues Band
weisse Streifen, grüner Rand
On Saturday January 3 2009 11:46:47 searchelite wrote:
Daniel Verite wrote:
searchelite wrote:
How about using
...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] De la part de Reg
Me Please
Envoyé : mardi 30 décembre 2008 17:09
À : Scott Marlowe
Cc : Scott Ribe; Gauthier, Dave; pgsql-general@postgresql.org
Objet : Re: [GENERAL] [PGSQL 8.3.5] Use of a partial indexes
Here it comes:
-- DDL
Only one question remains in my mind:
why the planner is not using the partial index?
The partial index is covering 2 predicates out of the 3 used in the where
condition. Actually there is a boolean flag (to exclude disabled rows),
a timestamp (for row age) and an int8 (a FK to another table).
December 30 2008 15:12:33 Scott Marlowe wrote:
On Tue, Dec 30, 2008 at 2:02 AM, Reg Me Please regmeple...@gmail.com
wrote:
Only one question remains in my mind:
why the planner is not using the partial index?
The partial index is covering 2 predicates out of the 3 used in the where
HI all.
I have a 8M+ rows table over which I run a query with a and-only WHERE
condition.
The table has been periodically VACUUMed and ANALYZEd.
In the attempt of speeding that up I added a partial index in order to limit
the size of the index. Of course that index is modeled after a slowly
that the slow performance returns.
Good Luck !
-dave
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Reg Me Please
Sent: Monday, December 29, 2008 9:09 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] [PGSQL
loss because of an external table needed for the partitioning.
On Friday December 19 2008 17:15:56 Merlin Moncure wrote:
On Fri, Dec 19, 2008 at 6:04 AM, Reg Me Please regmeple...@gmail.com
wrote:
Hi all.
I need to implement something very similar to temporal table partitioning
as described
Hi all.
I need to implement something very similar to temporal table partitioning as
described in the documentation at chapter 5.9.
My issues come from the fact that I have other tables that references (FKs) to
the table(s) to be partitioned. Those references are enforced by means of DRI
Hello all.
I have a number of tables that are actually dictionaries.
This means that, in order to keep the reference integrity, in a number of
other tables I have FK definitions like these ones:
CREATE TABLE dict1 ( d1 TEXT PRIMARY KEY, ... );
CREATE TABLE user1 ( d1 TEXT NOT NULL REFERENCES
Il Wednesday 15 October 2008 17:55:03 Tom Lane ha scritto:
Richard Broersma [EMAIL PROTECTED] writes:
For this reason, clients passing natural joins to the server can have
dangerous result sets returned with no warning.
Yeah. A lot of people consider that NATURAL JOIN is simply a bad idea
Hi all.
I'm running v8.3.3
First point.
Is there a way to know how a NATURAL JOIN is actually done?
That is, which fields are actually used for the join?
The EXPLAIN directive doesn't show anyting useful.
Second point.
I have this:
CREATE TABLE tab_dictionary ( item text primary key );
CREATE
Well, if it is a limitation, and having it would lead to a better product,
why not making it a feature for the next still-open release?
In my opinion that's more than a limitation, it's a missing feature.
In your code you often need to create savepoints to delay the decision for the
commitment.
Hi.
My humble opinion follows.
One point here is that the decision for the ROLLBACK could possibly be
different from errors.
It could simply be based upon a generic expression, not just the conditions
seen in Appendix A of the manual.
An exception is something different from a transaction,
Il Thursday 02 October 2008 16:15:10 Alvaro Herrera ha scritto:
Reg Me Please escribió:
Well, if it is a limitation, and having it would lead to a better
product, why not making it a feature for the next still-open release?
Because no one is working on implementing it?
In my opinion
Il Thursday 02 October 2008 17:10:23 Alvaro Herrera ha scritto:
Reg Me Please escribió:
Il Thursday 02 October 2008 16:15:10 Alvaro Herrera ha scritto:
You can nest blocks arbitrarily, giving you the chance to selectively
rollback pieces of the function. It's only a bit more awkward
Hi all.
Is there a way to have (sub)transactions within a function body?
I'd like to execute some code (a transaction!) inside a function and later
decide whether that transaction is to be committed or not.
Thanks.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
the cursor is read-only.
In my very humble opinion.
On Thursday 25 September 2008 19:58:07 Pavel Stehule wrote:
Hello
try to look at
http://okbob.blogspot.com/2008/08/using-cursors-for-generating-cross.html
regards
Pavel Stehule
p.s. you should to use transaction
2008/9/25 Reg Me Please
Hi all.
Is there a way in PL/PgSQL to get the number of rows resulting from a:
OPEN curs1 SCROLL FOR EXECUTE query;
before actually fetching any?
Unuckily
MOVE LAST FROM curs1;
won't work with
GET DIAGNOSTICS cnt = ROW_COUNT;
Any hint?
--
Sent via pgsql-general mailing
Hi all.
I'm running PGSQL v.8.3.3
I tried to adapt the examples from the friendly manual (38.7.3.5) in order to
to have a function to create cursors based on a parametric query string:
CREATE SEQUENCE s_cursors;
CREATE OR REPLACE FUNCTION f_cursor( query text, out curs refcursor )
LANGUAGE
NOthing bad, except that a number of tables are actually unreadable and some
code example lines are going past the right margin.
Apart of this, I would say it's great documentation.
On Sunday 21 September 2008 11:52:44 Sven Marcel Buchholz wrote:
Michelle Konzack schrieb:
Hello,
I am
Any hint?
Hi all.
I usually create indexes accordingly to the queries used in my software.
This means the more often than not I have composited indexes over more than
one column.
What'd be in PGSQL (v8.3+) the pros and cons of having instead only
one-column indexes?
Thanks in advance.
As I told you, I use to design indexes based upon the queries, the WHERE
clauses especially.
My fear is that in PGSQL the runtime index composition can be a drawback to
the performances if compared to static index composition.
Is this true accordingly to your experience?
Is there any best
Hi all.
Is there a way with the libpq to access subcolumns in a composite type
column?
The documentation (8.2) seems not to mention this case.
Thanks.
--
Reg me, please!
---(end of broadcast)---
TIP 4: Have you searched our list archives
the results from f_compo() into
the table TAB along with a value x.
I expected somthing like this to work:
insert into tab
select 42,row( c.* ) from f_compo() c;
But I get
ERROR: cannot cast type record to compo
Any hint?
TALIA
--
Reg me, please!
---(end of broadcast
Hello all.
I have some tables that contain exactly 1 row and that I use for searches with
JOIN.
Does it make any sense to hint the planner about this?
If so, how can I send such hints to it?
--
Reg me, please!
---(end of broadcast)---
TIP 9
this COPY?
--
Reg me, please!
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Il Wednesday 26 December 2007 12:58:34 Reg Me Please ha scritto:
Hi all.
I have this composite type:
create type ct as (
ct1 text,
ct2 int
);
Then I have this table
create table atable (
somedata numeric,
otherdata text,
compo ct
);
when I try to COPY data to that table
Il Wednesday 26 December 2007 14:31:04 Reg Me Please ha scritto:
Il Wednesday 26 December 2007 12:58:34 Reg Me Please ha scritto:
Hi all.
I have this composite type:
create type ct as (
ct1 text,
ct2 int
);
Then I have this table
create table atable (
somedata
DEFAULT 'INFINTY'
);
CREATE INDEX i_story_base
ON story_base( flag,starting,ending );
CREATE TABLE atable (
sometext TEXT,
LIKE story_base INCLUDING DEFAULTS
);
I'd like atable to also inherit an index like the one defined for
story_base.
Any hint?
--
Reg me, please
this necessary, or could I save some of them (maybe
just the DEFAULT) with no speed cost?
Is there a way to automate this by using the information_schema?
Many thanks in advance.
--
Reg me, please!
---(end of broadcast)---
TIP 1: if posting/reading through
Il Thursday 13 December 2007 19:56:02 Tom Lane ha scritto:
Reg Me Please [EMAIL PROTECTED] writes:
In order to speed up the COPY ... FROM ... command, I've
disabled everything (primary key, not null, references, default and
indexes) in the table definition before doing the actual COPY
and then re-creating both indexes and
constraints.
Is there a way to suspend the index updates and the constraint checks
before the inserts in order to later re-enable them and do a reindex?
TIA.
--
Reg me, please!
---(end of broadcast)---
TIP 4
Il Tuesday 04 December 2007 11:50:21 Peter Eisentraut ha scritto:
Am Dienstag, 4. Dezember 2007 schrieb Reg Me Please:
Is there a way to suspend the index updates and the constraint checks
before the inserts in order to later re-enable them and do a reindex?
You can disable foreign-key
.
Is there a better idea than mine? I hope so.
--
Reg me Please
Non quietis maribus nauta
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
)---
TIP 6: explain analyze is your friend
I presume that the usal LIMIT+OFFSET solution is not OK.
Right?
--
Reg me Please
Non quietis maribus nauta
---(end of broadcast)---
TIP 6: explain analyze is your friend
. An entity evaluates as good only when all property values in the
filter match the ones associated to an item in t_data.
What's missing to me is how to apply a filter to the t_data and get the list
of the items that evaluate good.
--
Reg me Please
Non quietis maribus nauta
Il Wednesday 21 November 2007 16:41:03 Rodrigo De León ha scritto:
On Nov 21, 2007 9:21 AM, Reg Me Please [EMAIL PROTECTED] wrote:
Hi all.
I've the following concept.
snip
This smells like EAV.
Please read
http://joecelkothesqlapprentice.blogspot.com/2006/04/using-one-table-vs-man
Il Wednesday 21 November 2007 20:22:46 Joe Conway ha scritto:
Reg Me Please wrote:
The meaning is that an entity called by the value of item has a number
of properties called by property with value prop_value.
So, for a single item there can be many different property each with
its own
: Have you searched our list archives?
http://archives.postgresql.org/
It's very likely that you have to do some explici casting on all other
paramter types, as the only one the DB has recognised is the last one,
aka TIMESTAMPTZ.
--
Reg me Please
Non quietis maribus nauta
Hi all.
What'd be the right place to put a feature request for the next releases and
for bugs in the current one?
Thanks.
--
Reg me Please
Non quietis maribus nauta
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ
Il Friday 16 November 2007 08:33:14 Tom Lane ha scritto:
Reg Me Please [EMAIL PROTECTED] writes:
The OP's complaint is that we don't allow a variable of the query's own
level, but AFAICT he's still not grasped the point that that leads to an
indeterminate limit value ...
So it works
Il Thursday 15 November 2007 14:09:16 Trevor Talbot ha scritto:
On 11/15/07, Reg Me Please [EMAIL PROTECTED] wrote:
In any case, what'd be the benefit for not allowing variables as LIMIT
and OFFSET argument?
When you can fully describe the semantics of your example, you'll
probably be able
In any case, what'd be the benefit for not allowing variables as LIMIT and
OFFSET argument?
--
Reg me Please
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining
Il Thursday 15 November 2007 17:55:42 Sam Mason ha scritto:
On Thu, Nov 15, 2007 at 05:34:43PM +0100, Reg Me Please wrote:
Il Thursday 15 November 2007 14:09:16 Trevor Talbot ha scritto:
On 11/15/07, Reg Me Please [EMAIL PROTECTED] wrote:
In any case, what'd be the benefit
Il Thursday 15 November 2007 20:28:17 hai scritto:
Reg Me Please wrote:
Sorry but I don't understand.
Either the LIMIT and OFFSET are to be definitely CONSTANT or not.
They must be constant during the execution of the query.
In the SQL function body the LIMIT and the OFFSET
into a LIMIT or
OFFSET. And under some circumstances (SQL function body) it's true even with
VARIABLE expressions like function call arguments.
In my opinion I would say it's more a problem with the syntax checker that
with the planner (semantics in my lingo). But I could be wrong.
--
Reg me Please
! :-)
--
Reg me Please
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
Il Thursday 15 November 2007 23:08:10 Richard Huxton ha scritto:
Reg Me Please wrote:
Il Thursday 15 November 2007 20:28:17 hai scritto:
Reg Me Please wrote:
In my opinion I would say it's more a problem with the syntax checker
that with the planner (semantics in my lingo). But I could
is not.
Wouldn't it be a nice enhacement to allow variable LIMIT and OFFSET in
SELECTs?
--
Reg me Please
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
than oracle tables?
Thanks
Sharmila
This's an interesting point fore sure as far as the data types for the two
table are comparable.
If this yelds true, the more space an RDBMS occupies, the slower the access.
I think.
--
Reg me Please
---(end of broadcast
/
--
Reg me Please
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
simpler.
Thanks a lot.
--
Reg me Please
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
Il Monday 12 November 2007 17:05:18 Dimitri Fontaine ha scritto:
Hi,
Le lundi 12 novembre 2007, Reg Me Please a écrit :
What I'd need to do is to filter t1 against f1 to get only the rows
( 'field1',1 ) and ( 'field2',1 ).
select * from t1 natural join f1 where t1.id = 1;
t| id
AND t1.id = x1.id));
Osvaldo
Nice, it seems to work. But I fear it won't with a longer f1 filter table.
Let me think about it.
--
Reg me Please
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
contains some 14M+ rows.
Would it be possible to get some reference or suggestion in order to
understand better the provided hint?
This is the very first time I see this message.
Many thanks.
--
Reg me Please
---(end of broadcast)---
TIP 9
.
I have no idea about pipelined functions.
--
Reg me Please
---(end of broadcast)---
TIP 6: explain analyze is your friend
Il Thursday 08 November 2007 17:09:22 Tom Lane ha scritto:
Reg Me Please [EMAIL PROTECTED] writes:
Il Thursday 08 November 2007 16:18:58 Tom Lane ha scritto:
It's either an int8 representing microseconds away from 2000-01-01
00:00:00 UTC, or a float8 representing seconds away from the same
there is a choice between int8 and float8 representation?
--
Reg me Please
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Il Wednesday 07 November 2007 07:54:41 Reg Me Please ha scritto:
Il Wednesday 07 November 2007 01:29:44 Alvaro Herrera ha scritto:
Reg Me Please wrote:
Il Tuesday 06 November 2007 22:13:15 hai scritto:
That's the branch and bound. Editing 29M+ lines file takes some time
Il Wednesday 07 November 2007 11:10:40 Dimitri Fontaine ha scritto:
Le mercredi 07 novembre 2007, Reg Me Please a écrit :
pgloader seems not that easy to use for a newbie like myself.
Also because domentation seems too skinny.
Sorry about this, writting documentation in English
Il Wednesday 07 November 2007 11:26:56 Dimitri Fontaine ha scritto:
Le mercredi 07 novembre 2007, Reg Me Please a écrit :
Maybe just a complete example would suffice. Let's say a table structure,
a CSV and a raw text file, a config file and the run output.
Do you mean something like
Il Tuesday 06 November 2007 19:05:52 Reg Me Please ha scritto:
Hi all.
I'm generating an SQL script to load some million rows into a table.
I'm trying to use the COPY command in order to speed the load up.
At a certain point I get an error telling about a
invalid input syntax for type
it be possible to avoid the so-called HTML email body?
--
Reg me Please
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
a plpgsql function for this.
--
Reg me Please
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing
Il Wednesday 07 November 2007 13:47:26 SHARMILA JOTHIRAJAH ha scritto:
Hi
we are testing with version PostgreSQL 8.2.3.
Why not using at least the current 8.2.5?
Read here
http://www.postgresql.org/docs/current/static/release.html
for details.
--
Reg me Please
Il Monday 05 November 2007 21:27:27 Reg Me Please ha scritto:
HI all.
While reading chapter 11 of v8.2 I've encountered this sentence:
However, if your server does not use the C locale you will need to create
the index with a special operator class to support indexing of
pattern-matching
Hi all.
What'd be the syntax to create a primary key on an already build table?
Thanks.
--
Reg me Please
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
cleanly
--
Reg me Please
---(end of broadcast)---
TIP 6: explain analyze is your friend
not
match
--
Reg me Please
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
While I would not spend resources in fine tuning the count(*), I would
spend some to underastand why and how the other ones do it better.
Just to be better.
Il Tuesday 06 November 2007 15:29:34 Bill Moran ha scritto:
In response to Reg Me Please [EMAIL PROTECTED]:
I have no doubt you're right
#cpu_operator_cost = 0.0025 # same scale as above
#effective_cache_size = 128MB
effective_cache_size = 4GB
The machine is a dedicated database server with two dual-core xeon
processors and 8 GB memory.
Thanks for your help,
Christian
--
Reg me Please
setf postgresql
Now all .psql files get the Posgres highlighting.
--
Reg me Please
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
1 - 100 of 127 matches
Mail list logo
