E SECURITY DEFINER RETURNS NULL ON NULL
INPUT;
SELECT testfunc();
ROLLBACK;
On Sat, Nov 22, 2008 at 1:37 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Rod Taylor" <[EMAIL PROTECTED]> writes:
>> DECLARE
>> v_time timestamp_with_precision;
>> BEGIN
>&g
The following bug has been logged online:
Bug reference: 4533
Logged by: Rod Taylor
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.5
Operating system: FreeBSD 7.0 Stable
Description:Plpgsql complex type failure
Details:
The below script should be able to
The following bug has been logged online:
Bug reference: 4182
Logged by: Rod Taylor
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: amd64-portbld-freebsd7.0, compiled by GCC cc (GCC) 4.2.1
20070719 [FreeBSD]
Description:Enum in Foreign
On Wed, 2004-10-20 at 14:07, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > troels=# create table lookat_feature(
> > troels(# feature_id char(4),
> > troels(# status varchar(2) default 'TODO'
> The alternative would seem to be decreeing that this is not a bug.
>
> C
> TRACE:
> The original tables are much bigger, so I've tried to simplify things here.
> Please let me know if there is anything that I could help you with.
You can't do that and expect to get reasonable results. The plans will
change with the volume of data.
Send an explain analyze of the true
On Thu, 2003-10-30 at 13:13, Peter Eisentraut wrote:
> Bas Scheffers writes:
>
> > When opening a file in psql, ~ (the user's home dir) is resolved when
> > using tab completion to find the file, but when you hit enter and psql
> > actualy tries to open it, you get a file not found error.
>
> Thi
On Tue, 2003-10-28 at 19:34, scott.marlowe wrote:
> On Tue, 28 Oct 2003, Tom Lane wrote:
>
> > "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > > Is it possible to remove the implicit search path of pg_catalog from a
> > > psql session without it breaking lots of stuff?
> >
> > Do you consider "+
On Tue, 2003-10-28 at 18:49, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I say leave it the way it is. If you want system table tab completion,
> > simply:
> > ALTER USER ... SET search_path =3D pg_catalog,...;
>
> Unfortunately, that *do
> Anyway, it seems like we need a vote to see how many people prefer
> each choice.
I say leave it the way it is. If you want system table tab completion,
simply:
ALTER USER ... SET search_path = pg_catalog,...;
I would like to see the information_schema be a part of the default
search_p
> Please enter a FULL description of your problem:
>
> When opening a file in psql, ~ (the user's home dir) is resolved when
> using tab completion to find the file, but when you hit enter and psql
> actualy tries to open it, you get a file not found
> NOTICE: adding missing FROM-clause entry for table "table_s1"
> NOTICE: adding missing FROM-clause entry for table "table_s2"
> and execution times explode, naturally. I don't know if the spec says
> this is the correct behavior or not, but I have a feeling its not and
> this is a bug.
This
On Sun, 2003-09-21 at 08:21, Ulrich Meis wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:pgsql-bugs-
> > [EMAIL PROTECTED] On Behalf Of Jean-Luc Lachance
> > Sent: Friday, September 19, 2003 4:44 PM
> > To: Rod Taylor
> > Cc: Ulrich Mei
> select * from quotes where id=1+round(random()* cast ((select max(id)
> from quotes) as double precision));
> id | quote |
> author
> -+---+--
> ---
> 187 | Vergib
On Fri, 2003-09-05 at 09:18, Bruno Wolff III wrote:
> On Wed, Sep 03, 2003 at 23:19:24 -0700,
> Ringo <[EMAIL PROTECTED]> wrote:
> > What a prick..
>
> >From observing Tom's responses here, I think this is a real question (not
> an RTFM response). If the documentation doesn't make it clear to ne
On Thu, 2003-08-21 at 07:55, Annu Panesar wrote:
> hi
> i need help urgently to understand how postgres manages its connection
> pool , how it manages deadlock . we are using postgres
See http://www.postgresql.org/docs/7.3/static/explicit-locking.html
Section 9.3.3 for DeadLocks.
signature.asc
D
> Wrong ! The query should return 4 rows. In other words i don't know
> why postgres performs the following query:
I think the syntax you're looking for is UNION ALL.
select a,b from t1 union all (select distinct a,b from t2);
signature.asc
Description: This is a digitally signed message part
ing column
creation, this will not work that way.
You could argue we should allow NOT NULL to be added to an empty table.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
scan on a very
small table is what you want to have.
In this particular case, vacuum removed over 11000 dead versions of the
tuple.
An 8 k page will hold approx 140 tuples based on your structure. So,
for every ~100 updates you'll want to run vacuum (regular, not full) on
the table
at or near "WITH" at character 38
> >
> > PS: I have downloaded the snapshot monday 24/03/2003
> >
> > Bye
> >
> > Laurent
> >
> >
> > Sample Code
> >
> >
> > No file was uploaded with this report
> >
> >
> >
omment to a database you presumably
> > already know (since you connected to it) does not seem to justify the
> > confusion it causes.
>
> Good analysis. Is removal actually the best solution?
Front-ends like pg_admin actually make pretty good use out of it.
--
Rod Taylor <[
lr%3Dlang_en%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff%26selm%3D04f201c1e7cc%25243479b2a0%25248001a8c0%2540jester%26rnum%3D1
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
>
> -> see that ri_triggers are vanished.
>
>
> No file was uploaded with this report
>
>
> ---(end of broadcast)---
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/f
On Sun, 2002-12-01 at 18:57, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > Adams patch is good. Please apply when you find time.
>
> I'm a bit confused by the patch --- it has a patch against "upgrade.pl"
> which is not to be seen in contr
On Sun, 2002-12-01 at 14:11, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > It makes sense, but I've not tested it yet.
>
> Okay, I'll hold off applying until you check it. It's not urgent,
> but I'd like to have it fixed in 7.3.1, which
the program and attached patches to
> > both original upgrade.pl and contrib/adddepend scripts.
>
> Rod, do you concur that this is a correct patch?
--
Rod Taylor <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
VACUUM FULL abba, but this didn't help. Thanks a lot for comments.
>
>
> P.S. btw, I upgrade my DBs from 7.2.1 to 7.3 version without any problems, but
> found, that psql's help messages (\h, \h alter table etc.) not from 7.3
> version. For example, it do not
h: 201-798-4983
> b. palmer, [EMAIL PROTECTED] pgp:crimelabs.net/bpalmer.pgp5
>
>
> __
>
> ---(end of broadcast)-------
> TIP 1: subscribe
exists in the view?
On Wed, 2002-11-20 at 10:49, Malcolm Hutty wrote:
> According to the manual you can stack multiple queries in a RULE:
> CREATE RULE R_DEL_AB AS
> ON DELETE TO V_AB
> DO INSTEAD
> (
> DELETE FROM A WHERE a_data=OLD.a_data;
> DELETE FROM B WHERE b_data=OLD.
rashed with fsync off, is to dump and
reload the database. This should clean up any data issues you currently
have -- assuming pg_dump functions on it.
That said, 7.2.3 has several vacuum fixes, but I don't think they'll fix
your problem.
--
Rod Taylor <[EMAIL PROTECTED]&g
ll affected tables.
You need to either:
ALTER TABLE RENAME "T_Tester_id_seq" TO t_tester_id_seq;
Or
ALTER TABLE "T_Joint"
ALTER COLUMN id
SET DEFAULT nextval('"T_Tester_id_seq"'::text);
The first converts the case of the sequence name to lower, the second
t dependency tracking mechanism. 7.4 should hold the fix for
pg_dump, although 7.3 has the dependency tracking mechanism.
--
Rod Taylor <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
her than trying to fetch
out max(obj_id).
select currval('object_list_obj_id_seq') AS nextvalue;
after the insert into object_list.
>
> $sth = $dbh->prepare("select max(obj_id) from object_list");
> $sth->execute();
> $ma
right direction.
For 7.2, use obj_id='100'. Quotes make the entry UNKNOWN which is
casted to int8 and should use the index.
--
Rod Taylor
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
--
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
>
--
Rod Taylor
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
cal row, you
probably want to use a trigger not a rule. Rules are most useful for
situations that call for transforming entire queries independently of
the specific data being handled.
Not that the description is obvious, but it's there. Perhaps you know
of a better way (place) to state t
ybe that
> has to be reopened because if we did that, it would make perfect sense
> because all SETs would be outside transactions.
Of course, the reason they're rollbackable is:
begin;
create schema newschema;
set search_path = newschema;
rollback;
creat
ATE T2 SET X=2 WHERE ID=1 AND T1=1;
>
> SELECT * FROM T2;
> SELECT * FROM T1;
>
> UPDATE T2 SET X=3 WHERE ID=1 AND T1=2;
>
> SELECT * FROM T2;
> SELECT * FROM T1;
>
> UPDATE T2 SET X=5 WHERE ID=2 AND T1=1;
>
> SELECT * FROM T2;
> SELECT * FROM
RT
> statements have no issues.
Try VACUUM FULL (different than regular VACUUM).
Try dumping data / shutdown daemon / fry data directory / initdb / start
daemon / restore data.
--
Rod Taylor
---(end of broadcast)---
TIP 3: if posting/read
.
Yup.. Your going to have to drop all of the views, then the column.
Or, ALTER TABLE ... DROP COLUMN .. CASCADE -- which will blow away the
views for you.
> On Fri, 2002-09-06 at 09:17, Tom Lane wrote:
> > Rod Taylor <[EMAIL PROTECTED]> writes:
> > > Indeed. At th
On Fri, 2002-09-06 at 09:17, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > Indeed. At the INNER JOIN it would appear that an alias is applied to
> > the columns of a given table.
> > ...
> > The real trick is to make INNER JOINS less greedy in th
Indeed. At the INNER JOIN it would appear that an alias is applied to
the columns of a given table.
{ RTE :alias { ALIAS :aliasname b :colnames <>} :eref { ALIAS :aliasname
b :colnames ( "col_b" "col_c" )} :rtekind 0 :relid 17194 :inh true
:inFromCl true :checkForRead true :checkForWrite fals
> > My understanding is that it's a single password, not a list.
>
> It isn't a single password. It is a file containing one password per
> line with pattern matching.
Oh, well in that case it should probably be a default spot in the home
directory.
---(end of broadcas
On Thu, 2002-09-05 at 12:14, Bruce Momjian wrote:
> Rod Taylor wrote:
> > On Thu, 2002-09-05 at 05:13, Reinhard Max wrote:
> > > On 4 Sep 2002 at 12:48, Rod Taylor wrote:
> > >
> > > > This item:
> > > > Add file to hold passwords using PGPA
On Thu, 2002-09-05 at 05:13, Reinhard Max wrote:
> On 4 Sep 2002 at 12:48, Rod Taylor wrote:
>
> > This item:
> > Add file to hold passwords using PGPASSWORDFILE environment variable
> >
> > Has been completed, and will be a part of the 7.3 release.
>
&g
This item:
Add file to hold passwords using PGPASSWORDFILE environment variable
Has been completed, and will be a part of the 7.3 release.
Thanks,
Rod
On Wed, 2002-09-04 at 11:54, [EMAIL PROTECTED] wrote:
> Wojciech Scigala ([EMAIL PROTECTED]) reports a bug with a severity of 4
> The lo
7.3 will partially fix this issue by extending the length of the NAME
data type.
Ie. You won't hit it until you have large (32+ character) length names.
On Tue, 2002-09-03 at 16:31, [EMAIL PROTECTED] wrote:
> Søren Laursen ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the n
Single single quote literals, double quote literals.
'profiles' => "profiles"
On Tue, 2002-09-03 at 10:56, * * wrote:
> I'm getting the error ERROR: parser: parse error at or near "'"
> This is my sql statement in my servlet and i don't see what's wrong with it.
>
> SQL = "Select users.first_n
> Can tab completion be disabled without disabling command line history? I
> noticed -n disables both. I would gladly trade tab completion for tab
> pastability, but I rely heavily on command line history.
Perhaps annoying, but a simple work around is to use
Formats like tab in the code, b
The problem is that most items in postgresql are tab completed.
Cut and past your text into a bash or zsh prompt. It injects a bunch of
filenames into your data, as per tab completion.
Annoying, but for the benefits it's livable.
Perhaps a toggle could be created to disable tab completion?
O
at all -- which shouldn't be
an issue as there is still the unique.
Not the brightest thing to do, but surely the primary key shouldn't be
enforced to exist before a plain old unique.
If thats the case, then unique indecies need to be blocked until there
is a primary key, or the first one
-- I just tell how).
Anyway, any crash is a bad crash I suppose.
--
Rod Taylor
Your eyes are weary from staring at the CRT. You feel sleepy. Notice
how restful it is to watch the cursor blink. Close your eyes. The
opinions stated above are yours. You cannot imagine why you ever felt
51 matches
Mail list logo
