> http://www.ca.postgresql.org/sitess.html
> says that:
> The current version of PostgreSQL is 7.2.1.
> NOTE: An initdb will only be required if upgrading from pre 7.2
>
> So, if my current version is 7.2.0 and I want upgrade it to
> 7.2.1, what file should I download in order to get 'intidb'?
> i
Hi Ligia,
When I need to do this I use a scripting language like PHP, Perl or
ColdFusion to
select from one db and insert into another.
As a matter of fact I had to do this exercise just yesturday.
I like it as I find I have much more freedom to gather data, organise it
then insert it.
It's eas
> Forgot to mention that adding
> DROP TABLE v_idx ;
> before the END WORK will fix things. However, I was under the
> impression that
> temporary tables would go away after a transaction in which they
> were created
> was committed.
No - they go away at the end of a _connection_. However, ther
On Wed, 3 Jul 2002, [ISO-8859-1] Magnus Sjöstrand wrote:
> Hi,
>
> I have a table as:
> create table sections (
> id serial not null primary key,
> parent_idreferences sections(id)
> );
>
> there is only one row where the parent_id is NULL, and that is the root
> section,
http://www.ca.postgresql.org/sitess.html
says that:
The current version of PostgreSQL is 7.2.1.
NOTE: An initdb will only be required if upgrading from pre 7.2
So, if my current version is 7.2.0 and I want upgrade it to
7.2.1, what file should I download in order to get 'intidb'?
if only the
When using the attached script in psql, the temp variables disappear as
far as \distv shows, but running the script a second time fails.
To reproduce, save the following script as bug.sql, then start psql on an
test database.
\i bug.sql
\distv
-- no relations should be shown
\i bug.sql
-- this
I'm on a Linux RH 7.2 system, which came with Pg 7.1.2 (I think). When
there, I prototyped some code that worked well, and looked like:
create table ref_sp
(
name varchar(10),
sname char(1),
bitmask bit(6)
);
insert into ref_sp values ('one', '1', b'01');
insert into ref_sp
Ligia Pimentel wrote:
> I don't know if this can be done...
>
> In MSSQL Server I can access a table created in another database (on the
> same server, of course) by using the following syntaxis...
>
> select * from databasename..tablename where condition;
>
> Can I do this in postgres?
>
> I'
Forgot to mention that adding
DROP TABLE v_idx ;
before the END WORK will fix things. However, I was under the impression that
temporary tables would go away after a transaction in which they were created
was committed.
---(end of broadcast)---
OK, we figured it out.
The problem is the documentation confused me!!!
In man page of pg_restore:
-P function-name
--function=function name
Specify a procedure or function to be restored.
User will assume that syntax of restoring a function is same as
restoring a table, but it's not tru
Hi,
I have a table as:
create table sections (
id serial not null primary key,
parent_idreferences sections(id)
);
there is only one row where the parent_id is NULL, and that is the root
section, all others refers to a section. Now I want to create a trigger,
so that wh
I don't know if this can be done...
In MSSQL Server I can access a table created in another database (on the
same server, of course) by using the following syntaxis...
select * from databasename..tablename where condition;
Can I do this in postgres?
I'm using version 7.2 on a redhat server...
GRIMOIS Eric wrote:
> Hi all
>
> Is there a simple way to localize in foreign language error messages without
> modifying and compiling the sources again ?
> It should be useful for final users who don't read Shakespeare in the
> original version ;)
Uh, we have error messages localization in 7.2
This is not the case, because those db on a same server, it's
I dump data from one db and try restore one of it function into
another db.
Thanks for your response anyway.
Jie Liang
-Original Message-
From: Achilleus Mantzios [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 03, 2002 12:
Hi all
Is there a simple way to localize in foreign language error messages without
modifying and compiling the sources again ?
It should be useful for final users who don't read Shakespeare in the
original version ;)
Eric GRIMOIS
Analyste programmeur
SEI - CPAM du Val d'Oise
--
On Tue, 2 Jul 2002, Ahti Legonkov wrote:
Check the actual time by explain analyze.
If sequential scan (your table is small e.g.) is faster
then there is no need for index use.
Also check the enable_indexscan variable.
> Hi,
>
> I have this query:
> select * from reo inner join usr on reo.owner_
In the case that you moved your backup to another system
where possibly the shared library (.so) where the function exists is on a
different location then thats the problem, in which case you only need
to recreate the function (with the same isstrict,iscachable attributes).
--
Achilleus Mantzio
1. ANALYZE both tables. Go 'VACUUM ANALYZE;' to vacuum and analyze your
tables. Analyzing means to update the planner statistics for the tables,
which might make Postgres use your indices.
2. If you tables are very small (eg. only a few hundred rows) then using an
index is usually slower than j
Hi Ricardo,
I assume you're talking about foreign key constraints?
Dropping a constraint is a real pain in all versions of Postgres up to and
including 7.2.1.
You will need to manually drop the RI trigger on the child table and the two
triggers on the parent table.
Techdocs has some informatio
Hi list,
I need your help.
How I can delete or DROP a constraint?
I use POSTGRESQL 7.0.3
_
MSN. Más Útil cada Día. http://www.msn.es/intmap/
---(end of broadcast)---
TIP 6: Have y
20 matches
Mail list logo
