Andrew Dunstan wrote:
Vinay Jain wrote:
You mean that I should create a static table in C program itself and
use it...if i am not wrong
Ya for the time being i am doing this thing but actually table is
bigger (around 5000 rows with 6 columns)
bigger than what?
also this table is also
I have a table with a tsearch2 index on it. Now, I have all the
tsearch2 stuff installed into a 'contrib' schema. I have had to change
the default database schema to include the contrib schema as
behind-the-scenes, tsearch2 looks for its tables, and cannot find them
even if the function
Thanks Christopher,
we'll look into the issue.
Oleg
On Fri, 7 May 2004, Christopher Kings-Lynne wrote:
I have a table with a tsearch2 index on it. Now, I have all the
tsearch2 stuff installed into a 'contrib' schema. I have had to change
the default database schema to include the
Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
What about rules/views/functions and who knows what else (domains?)
might be dependant on the current type definition?
Yeah, I was just thinking about that this morning. We probably ought to
look for dependencies on the table rowtype as
Christopher Kings-Lynne wrote:
Just a note for the hackers, Jonathan (I think :) ) talked to me about
this on the irc channel - we couldn't figure this one out. Seems that
Exist a postgres irc server? If yes may I know the server and port ?
Regards
Gaetano Mendola
Hi all,
today I was tryng to delete an index but I had the following
error:
ERROR: cannot drop index activation_code_code_key because constraint activation_code_code_key on
table activation_code requires it
HINT: You may drop constraint activation_code_code_key on table activation_code instead.
FireBird: ALTER COLUMN column TYPE type
DB2: ALTER COLUMN column SET DATA TYPE type.
Oracle: MODIFY column type
MSSQL:ALTER COLUMN column type constraints
MySQL:Both Oracle and MSSQL
Sap: MODIFY column type
Spec: Nothing (obvious) on changing column types
Vinay Jain said:
Andrew Dunstan wrote:
uh ... maybe you need to look in your C manual about the effect of a
static declaration. The object will be created once.
yup I know the effect of Static but this is also fact that when
program terminates and restarts object will be created
Andrew Dunstan wrote:
Vinay Jain said:
Andrew Dunstan wrote:
uh ... maybe you need to look in your C manual about the effect of a
static declaration. The object will be created once.
yup I know the effect of Static but this is also fact that when
program terminates and restarts
Gaetano Mendola said:
Christopher Kings-Lynne wrote:
Just a note for the hackers, Jonathan (I think :) ) talked to me about
this on the irc channel - we couldn't figure this one out. Seems
that
Exist a postgres irc server? If yes may I know the server and port ?
Vinay Jain said:
Andrew Dunstan wrote:
If course it is not loaded each time. That would be insane. If not
preloaded it is loaded when first called in each process, and then
kept. It is never unloaded (except by the termination of the process
that loaded it).
It seems you have been laboring
Andrew Dunstan wrote:
Vinay Jain said:
Andrew Dunstan wrote:
If course it is not loaded each time. That would be insane. If not
preloaded it is loaded when first called in each process, and then
kept. It is never unloaded (except by the termination of the process
that loaded it).
It
Alvaro Herrera wrote:
On Fri, May 07, 2004 at 12:31:51AM +0200, Umberto Zappi wrote:
Thanks to everybody has reply to my email.
Stop immediatly my work in progress.
Some days ago I've downloaded version 7.4.3 of postgresql and I've begin
to work over without know other jobs of other developers
Joshua D. Drake wrote:
Personally, plpgSQL is only useful to those who are coming from Oracle.
People are more likely to be comfortable with plPython or plPerl than
plpgSQL.
Well that was not true for my, I started using postgres and plpgsql
not because I knew Oracle ( I don't know it ).
plpgsql
plpgsql is more close to postgres then plPython or plPerl, and after
all is nearest SQL then plPtyhton or plPerl so a DBA find it more
confortable then others languages.
DBA probably... programmer? Doubtful. The majority of people that I run
into that are using PostgreSQL are not DBA's. They are
Joshua D. Drake wrote:
plpgsql is more close to postgres then plPython or plPerl, and after
all is nearest SQL then plPtyhton or plPerl so a DBA find it more
confortable then others languages.
DBA probably... programmer? Doubtful. The majority of people that I run
into that are using
On Fri, May 07, 2004 at 03:09:58PM +0200, Gaetano Mendola wrote:
Alvaro Herrera wrote:
On Fri, May 07, 2004 at 12:31:51AM +0200, Umberto Zappi wrote:
Thanks to everybody has reply to my email.
Stop immediatly my work in progress.
Some days ago I've downloaded version 7.4.3 of postgresql
Tom Lane wrote:
Actually, no, I'd prefer not to make such a distinction; I'd be happy
with SQL-level PREPARE being nontransactional. I'd be willing to put
up with that distinction if someone shows it's needed, but so far
there's not been a really good argument advanced for it, has there?
Has
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Just a note for the hackers, Jonathan (I think :) ) talked to me about
this on the irc channel - we couldn't figure this one out. Seems that
pg_dump produces NATURAL CROSS JOIN in the dump of a view, but the pgsql
grammar
Shachar Shemesh wrote:
Just out of curiosity, how do I manually destroy the cursor when it's no
longer needed? Just do close refcursor?
Yup:
http://www.postgresql.org/docs/current/static/sql-close.html
Also, does this copy take place when the table is changed, or as soon as
the transaction
Fabien COELHO wrote:
Please find attached as somehow requested a plpgsql implementation
for a high-level description (by that, I understand relationnal,
not functionnal) of acl in postgres.
That doesn't tell me anything. The functionality of the ACL system is
to answer questions like does
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
During the irc discussion I discovered that. But the CREATE TABLE page
in the docs appears to suggest that it is legal. That should be fixed.
Where exactly? I see
For the INNER and OUTER join types, a join condition must be
Hi all,
I with to write a new builtin type, I seen that what I have to do is:
1) ad on pgsql/src/include/utils/builtins.h
the signature for my function that will manipulate my
type
2) ad on pgsql/src/backend/utils/adt
a new file my_type.c
with the implementation of all function
Hi Bruce,
Sorry for the confusion because Rod asked a question
and I answered too quickly. This is what I mean.
15x Slower:
---
Client --TCP-- PgPool --UNIX-- PostgreSQL
Client --TCP-- PgPool --TCP-- PostgreSQL
5x Faster:
--
Client --UNIX-- PgPool --UNIX--
24 matches
Mail list logo
