DaVinci wrote:
> create function pilpot(calle) returns integer as '
this is your problem. try this:
create function pilpot(text) returns integer as '
the syntax for creating postgres functions is to declare the types, not
the identifiers of any parameters.
-tfo
-
> Adding a LIMIT 1 in the subplan may also help -- as you only need a
> single match to make it true so additional finds are useless -- it'll
> stop sooner or will be more likely to use an index than a full table
> scan.
> --
> Rod Taylor
I'm not sure if I understand you correctly here: the subp
On Mon, Apr 16, 2001 at 03:43:23PM +0200, DaVinci wrote:
> Hello.
>
> When I create next function:
>
> create function pilpot() returns integer as '
> declare
> foo integer;
> begin
> foo = insert into aviso(user) va
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Rini Dutta <[EMAIL PROTECTED]> writes:
> > Here is the performance statistics on the same
> table.
> > Note the fall in performance as the test proceeds.
>
> Try 7.1. I think you are running into the
> lots-of-pending-triggers
> problem that was found a
On Mon, Apr 16, 2001 at 04:39:50PM +0200, Peter Eisentraut wrote:
> Patrick Dunford writes:
>
> > Zeos Database Explorer shows the type of these fields to be "bpchar", is
> > this a Postgres data type?
>
> bpchar is the internal name for char().
short for "blank-padded character". as opposed to
> I receive this error when trying to pg_dump -s
>
> failed sanity check, table answers was not found
>
> the failed table name varies. All the problematic tables
> seem to work. vacuumdb (-z) also works without any comment.
>
I had some similar problems with pg_dump on 7.0.3 rec
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> Adding a LIMIT 1 in the subplan may also help -- as you only need a
> single match to make it true so additional finds are useless -- it'll
> stop sooner or will be more likely to use an index than a full table
> scan.
I believe this is not necessary; th
=?iso-8859-2?Q?Marek_P=EAtlicki?= <[EMAIL PROTECTED]> writes:
> I receive this error when trying to pg_dump -s
> failed sanity check, table answers was not found
I suspect you have a table whose owner no longer exists in pg_shadow.
Check the pg_class.relowner value for that table, and creat
Adding a LIMIT 1 in the subplan may also help -- as you only need a
single match to make it true so additional finds are useless -- it'll
stop sooner or will be more likely to use an index than a full table
scan.
--
Rod Taylor
There are always four sides to every story: your side, their side, the
I'm trying to back up a table by dumping to a text
file,
but in the proccess of dumping I get the following
error
dumpSequence(pilgram_en_id_seq): different sequence
name returned by SELECT: pilgram_cross_id_seq
I'm not sure what this means, and I have no idea
how to corect it.
Mike
"David M. Kaplan" <[EMAIL PROTECTED]> writes:
> ... If you do that, you
> can no longer do things like restores from backups without editing the
> configuration file because postgresql wont let you change users. This is of
> course not a great problem, but it is a bit annoying. What I really wan
Michael McDonnell <[EMAIL PROTECTED]> writes:
> And when I run "SELECT contactable_name(1);" I get the error message
> "parse error at or near $1".
$1 is a parameter placeholder; probably your problem is unexpected
substitution (or lack of substitution) of a plplgsql variable or
parameter into a
Christian Fritze <[EMAIL PROTECTED]> writes:
>explain select * from allmain where exists (select distinct
>dokids_as_int from allslwfull where dokids_as_int = idn and
>wort_nouml_lower like 'gen%')
Try dropping the "distinct" on the inner select. As a moment's thought
will reveal,
Hi,
I was comparing speed of inserts in C vs JDBC and
found that as the table size increases the speed
differential decreases till there is no difference (no
problem). However inserts kept getting slower and
slower as the table size increased and the performance
became quite poor. Here is the dat
"David M. Kaplan" <[EMAIL PROTECTED]> writes:
> Even better would be that postgres uses the standard unix security
> and that on connecting it asks for the appropriate unix password unless you
> are a superuser in which case it just connects.
This would tie Postgres usernames to usernames of the
I receive this error when trying to pg_dump -s
failed sanity check, table answers was not found
the failed table name varies. All the problematic tables
seem to work. vacuumdb (-z) also works without any comment.
This is a production database on 7.0.3
I'd like to migrate to 7.1, but I a
On Tue, Apr 17, 2001 at 09:23:02AM -0300, Marcelo Pereira wrote:
> Hi All,
>
>
> Now I would like to select all employees which name begins with the letter
> "P".
>
> > Select * from employee where "name-begin-with-letter-P" :-)
>
select * from employee where email ~ '^P';
or if cas
SELECT * FROM employee WHERE empname LIKE 'P%'
the above would work only if you want to search for people w/ names starting
w/ P
Mike
- Original Message -
From: "Marcelo Pereira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 17, 2001 5:23 AM
Subject: Select
> Hi All
Hi All,
I'm in trouble to build a select...
I have a table (for example) like this:
Table: Employee
empCod | empName | empDepth
-+---+---
1 | Anand |any
2 | Oliver |any
3 |Peter |any
4 | Bo
Hello.
I am trying to insert a tupla in a view with rules for inserting from a
function. This is my data:
---
create table dirección (
cod serial primary key,
calle text,
vía int2refe
hi Bob,
Try
psql -h -U -f
HTH
Anand
On Mon, Apr 16, 2001 at 12:36:06PM -0700, Bob McCormick wrote:
>All,
>
>I've found a case tool that will generate a schema based on PostgreSQL
>syntax and am wondering if it is possible to run this generated SQL script
>to have the database schema create
On 12 Apr 2001, at 0:00, Justin Clift wrote:
>
> Any there any people who can understand both english and non-english
> languages, who wouldn't mind translating an article or two on the
> techdocs.postgresql.org website to a different language?
>
I would gladly do some translation in italian. Wh
Firestar wrote:
> Hi,
>
> I'm currently using PostgreSQL 7.0 on Solaris. My Java program receives
> strings in Big5
> encoding and will store them in PostgreSQL (via JDBC). However, the inserted
> strings become
> multiple '?' (question marks) instead everytime i do a insert command. And
> when i
23 matches
Mail list logo
