On 24 Jul 2003 at 10:00, Tom Lane wrote:
Richard Huxton [EMAIL PROTECTED] writes:
There's a multi-year plan to bring the code bases closer together which
sounds like one of those big projects that always make me nervous.
Just between us chickens, I hope they do spend multiple man-years
Terence Chang schrieb:
I am still getting the error. would this matter with 7.3.3 on windows with
cygwin?
From my experience I'd never user quotes at any place (neither during creation
of the table nor in the SELECT, UPDATE statements). All DBMS I know behave like
Postgres. So if you never quote
Hello all,
just out of curiosity: how can I find out which files in the PG_DATA directory
belong to which database/table?
I have looked through the documentation of the system catalogs, but couldn't
find any reference to that.
The field datpath in pg_database is empty in my system (7.2 on
On 25 Jul 2003 at 8:45, Thomas Kellerer wrote:
just out of curiosity: how can I find out which files in the PG_DATA directory
belong to which database/table?
There is a contrib module oid2name. Use that.
You can just find the oid of the object from catalog and search for that file.
That's
just out of curiosity: how can I find out which files in the PG_DATA
directory belong to which database/table?
I have looked through the documentation of the system catalogs, but couldn't
you should also look through the mailing list archives...
Karsten
--
GPG key ID E4071346 @
Shridhar Daithankar schrieb:
On 25 Jul 2003 at 8:45, Thomas Kellerer wrote:
just out of curiosity: how can I find out which files in the PG_DATA
directory belong to which database/table?
There is a contrib module oid2name. Use that.
You can just find the oid of the object from catalog and
Hi.
I've made a small stored procedure un PL/python. This procedure retrieve
python code from a row then execute it and calls a predefined function.
Alls works well while no others functions are defined and called in the row
retrieved code; I mean when I define the row retrieved
On Thu, Jul 24, 2003 at 04:34:26PM -0700, Terence Chang wrote:
All:
I don't remember I even seen a document saying PostgreSQL are case
sensitive. I just figure out that my column name are case
The docs have it in a footnote:
As mentioned previously I have a large text database with upwards of
40GB of data and 8 million tuples.
The time has come to buy some real hardware for it.
Having read around the subject online I see the general idea is to get
as much memory and the fastest I/O possible.
The buget for the
On Fri, 2003-07-25 at 07:28, Andrew Sullivan wrote:
On Thu, Jul 24, 2003 at 04:34:26PM -0700, Terence Chang wrote:
All:
I don't remember I even seen a document saying PostgreSQL are case
sensitive. I just figure out that my column name are case
The docs have it in a footnote:
Hi All,
I have posted this before, but have not yet got any resolutions on it. I am
hoping someone with experience can help me out.
I am running Postgresql 7.3.2 on Solaris 5.9. I am trying to increase the
number of max connections for postgresql but it but
I am having some issue. After reading
On Thursday 24 July 2003 02:59 pm, Franco Bruno Borghesi wrote:
You must install pgcrypto (its in your contrib/pgcrypto directory).
Then, the functions crypt and gen_salt will become available.
As an example, to insert a new user (peter) with an encrypted password
(1234) you can do:
INSERT
Thomas Kellerer [EMAIL PROTECTED] writes:
Shridhar Daithankar schrieb:
You can just find the oid of the object from catalog and search for that
file. That's the principle.
That easy ? :-)
Actually you must look at pg_class.relfilenode; this is initially the
same as oid, but there are
On Friday 25 July 2003 02:37 am, Thomas Kellerer wrote:
Terence Chang schrieb:
I am still getting the error. would this matter with 7.3.3 on windows
with cygwin?
From my experience I'd never user quotes at any place (neither during
creation of the table nor in the SELECT, UPDATE
On Fri, 2003-07-25 at 07:42, [EMAIL PROTECTED] wrote:
As mentioned previously I have a large text database with upwards of
40GB of data and 8 million tuples.
The time has come to buy some real hardware for it.
Having read around the subject online I see the general idea is to get
as
On Fri, 25 Jul 2003 09:33:30 -0400 Reuben D. Budiardja [EMAIL PROTECTED] wrote:
I think if you encrypt MD5 before storing it into the table, then there
is no
way to retrieve the corresponding clear text right? since MD5 is one-way
encryption..
yes, but normally when doing passwords, one
Errol Neal [EMAIL PROTECTED] writes:
After making this change, and increasing the max number of buffers to
128 and the max number of connections to 64, I rebooted my
system. Things come up fine, Postgres seems happy, but shortly after
the Postgres server dies or terminates with nothing in
Ron Johnson [EMAIL PROTECTED] writes:
On Fri, 2003-07-25 at 07:28, Andrew Sullivan wrote:
The docs have it in a footnote:
http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-syntax.html#FTN.AEN1031
PostgreSQL's approach is backwards from the standard.
Is there any firm discussion about
This is exactly what I was doing. I use PostgreSQL Manager Pro. The tool
covert all my column name and table name in the double quote. So I have all
my column/table/function created in upper case (Oracle habit). Now, I have
to quote all of them.
I should stay with psql, I guess. :-)
Thanks! At
The first query is able to use the index on nr_proponente, because the
condition involves that column directly, the second query is not,
because the index only contains the values of nt_proponente, not results
of trunc(..)/
Try replacing that condition with something like
pa.nr_proponente
Hi
all!
What can I do in this
case?
I could not found anything about
iscachable.
postgres$ cat
in.sqlcreate index bt_proposta_f01 on propostausing btree
(func_cod_secretaria(nr_proponente));
postgres$ psql
-d escola -f in.sqlpsql:in.sql:2: ERROR: DefineIndex: index function
must be
On Fri, 25 Jul 2003, Elielson Fontanezi wrote:
What can I do in this case?
I could not found anything about iscachable.
postgres$ cat in.sql
create index bt_proposta_f01 on proposta
using btree (func_cod_secretaria(nr_proponente));
postgres$ psql -d escola -f in.sql
On Fri, 25 Jul 2003, Stephan Szabo wrote:
On Fri, 25 Jul 2003, Elielson Fontanezi wrote:
What can I do in this case?
I could not found anything about iscachable.
postgres$ cat in.sql
create index bt_proposta_f01 on proposta
using btree (func_cod_secretaria(nr_proponente));
Oh sorry!
Linux netlab142.prodam 2.4.8-26mdk #1 Sun Sep 23 17:06:39 CEST 2001
i686 unknown
pg_ctl (PostgreSQL) 7.2.1
-Mensagem original-
De: Stephan Szabo [mailto:[EMAIL PROTECTED]
Enviada em: sexta-feira, 25 de julho de 2003 16:25
Para: Elielson Fontanezi
Cc:
Stephan Szabo [EMAIL PROTECTED] writes:
You're probably ending up with different plans since in one case it has
a plain column reference and in the other it has a marginally complicated
expression in the join condition.
Yeah. 7.3 and before cannot do merge or hash joins on conditions that
are
Hi!
Who can help me on that?
First of all, my envoronment
is:
Linux
netlab142.prodam 2.4.8-26mdk #1 Sun Sep 23 17:06:39 CEST 2001 i686
unknown pg_ctl (PostgreSQL)
7.2.
Problem: ERROR: DefineIndex:
index function must be marked iscachable by
executing:
create index bt_proposta_f01
On Fri, 25 Jul 2003, Elielson Fontanezi wrote:
Who can help me on that?
First of all, my envoronment is:
Linux netlab142.prodam 2.4.8-26mdk #1 Sun Sep 23 17:06:39 CEST 2001
i686 unknown
pg_ctl (PostgreSQL) 7.2.
You should definately move to the highest 7.2 release
Thanks a lot!
The complete solution is here!
1st. The function wich substitute the trunc() function
CREATE OR REPLACE FUNCTION func_cod_secretaria(INTEGER) RETURNS INTEGER AS '
DECLARE
v_nr_proponente ALIAS FOR $1;
BEGIN
return TRUNC(v_nr_proponente/10,0)*10;
END;
'
Questions:
1) If you have an index on a cacheable function, does PostgreSQL use the
index instead of calculating the results?
2) How does PostgreSQL know when to recompute the function?
Jon
On Fri, 25 Jul 2003, Elielson Fontanezi wrote:
Thanks a lot!
The complete solution is here!
1st.
On Fri, 25 Jul 2003, Maksim Likharev wrote:
I have 2 queries, one is never returns, like explain shows 677195846.00
cost
and another doing the same job works ( cost 6072.00 )
I do not understand one thing, why query number one, generates so
unbelievably
screwed up plan?
why it does
My be I too spoiled by MS SQL Server, but does'nt
syntax:
update prod.t_results set expdate=e.termdate from
work.termdate e, prod.t_results r where e.docid=r.docid;
or
update prod.t_results set expdate=e.termdate from
work.termdate e inner join prod.t_results r on
Bruce Momjian [EMAIL PROTECTED] writes:
It would be nice to specify the input and output formats independently.
They are independent now.
I think we can sort of do that now, but it isn't clear. When format is
Postgres, US/European control whether month is first in input and
output. When it
Maksim Likharev wrote:
My be I too spoiled by MS SQL Server, but does'nt
syntax:
update prod.t_results set expdate=e.termdate from
work.termdate e, prod.t_results r where e.docid=r.docid;
or
update prod.t_results set expdate=e.termdate from
work.termdate e inner join
On Fri, 25 Jul 2003, Maksim Likharev wrote:
My be I too spoiled by MS SQL Server, but does'nt
syntax:
update prod.t_results set expdate=e.termdate from
work.termdate e, prod.t_results r where e.docid=r.docid;
or
update prod.t_results set expdate=e.termdate from
work.termdate e
On Fri, 2003-07-25 at 18:55, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
It would be nice to specify the input and output formats independently.
[snip]
that I'm outvoted on that point). The point I'm trying to make is that
we need to extend input DateStyle so that this approach
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
It would be nice to specify the input and output formats independently.
They are independent now.
I think we can sort of do that now, but it isn't clear. When format is
Postgres, US/European control whether month is first in
Bruce Momjian [EMAIL PROTECTED] writes:
But we lose functionality that can't possibily be used in 2003 because
03-01-01 doesn't identify 03 as a year.
This argument is specious. You could equally well use it to justify
removing our support for dd-mm-yy and mm-dd-yy, because those aren't
unique
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
But we lose functionality that can't possibily be used in 2003 because
03-01-01 doesn't identify 03 as a year.
This argument is specious. You could equally well use it to justify
removing our support for dd-mm-yy and mm-dd-yy,
38 matches
Mail list logo
