Josh Berkus wrote:
Gaetano,
Hackers, what about to decrease the default values for this
quantities ?
Oh, I don't think Ismail has a bug, I think he probably just needs to tune his
database.
I just only suggesting to decrease that values that are oversized for a modern
hardware.
Regards
Ga
om command line, what you have to
do is decrease the cost of the index scan till is less of the sequential
scan cost.
Good luck.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if yo
alues that are good for a modern machine.
Hackers, what about to decrease the default values for this
quantities ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
ough in the initdb fase create the postgres user as
undeleateable.
I think this is resonable.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
icletbl;
SELECT COUNT(*) AS c FROM articletbl WHERE
mydate BETWEEN '2004-04-24' AND '2004-05-24';
SELECT COUNT(*) AS c FROM articletbl WHERE
mydate = '2004-04-24';
Regards
Gaetano Mendola
---(end of broadcast)---
TI
Win32 compared with other products? I really
hope yes, you know: there is no a *second* possibility to do a *first* good
impression.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
duction", am I wrong ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
ot;[EMAIL PROTECTED]" true o false?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Neil Conway wrote:
Gaetano Mendola wrote:
I well understand the reason to wait a 7.5 in order to delivery
BIG changes that are requiring a initdb, but I don't understand
why little enhancement can not be delivered in a 7.4.3 ( may be
with a short period with a 7.4.3beta ) like the "vacu
ering some improvements in the 7.4.3 will permit
to delay a month the 7.5 without the pain to wait too long for some
enhancements.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Hans-Jürgen Schönig wrote:
Somebody has posted sync multimaster replication (PgCluster) - nobody
has commented on that. Maybe I am the only one who has ever tried it ...
I didn't find it on pgFoundry, others place to look at it ?
Regards
Gaetano Mendola
---(e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Page wrote:
|>-Original Message-
|>From: Gaetano Mendola [mailto:[EMAIL PROTECTED]
|>Sent: 17 May 2004 16:02
|>To: Bruno Wolff III
|>Cc: [EMAIL PROTECTED]
|>Subject: Re: [HACKERS] Email data type
|>
|>About the dom
Greg Stark wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
Comments are welcomed.
Well as long as you're asking...
Email domains are case insensitive, but the left hand side is case sensitive.
That's the only part that's hard to handle using a text data type, it would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Wolff III wrote:
| On Sun, May 16, 2004 at 04:36:55 +0200,
| Gaetano Mendola <[EMAIL PROTECTED]> wrote:
|
|>The type is indexable and provide also conversion methods:
|>
|>text <--> email
|>and the operator >>, is
Gaetano Mendola wrote:
Hi all, this is the alpha version for the new email data type,
is not written as built in type but as plug in, Tome Lane and others
drove me in this direction.
The type is indexable and provide also conversion methods:
text <--> email
and the operator >>, is pos
x27;@' (it's an alpha version), I'd like
to put it on pgfoundry but apparently my DNS are unable to resolve
www.pgfoundry.org. I'll put this version as soon the address become
available.
This is the first time that I wrote code for postgresql so please, if
you can, do a sort
if
you can, do a sort of code revision on it.
Comments are welcomed.
=============
Regards
Gaetano Mendola.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Hi all,
what is the purpose of two function send and receive
when a new type is defined ? When these two functions
are called ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
IABLE. (Internally, this is represented by setting
typlen to -1.)
I'm doing this on Postgres 7.4.1
Am I missing something ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
which library I have to link in order to have the symbol pg_begintypsend ?
I think you want pq_begintypsend.
Consider paying more attention to unknown-function warnings from your
compiler.
I had no warning at all, I think I h
brary "emaildt.so": emaildt.so: undefined symbol:
pg_begintypsend
I'm compiling my files in this way:
gcc -c -g -fPIC -o "email.o" -I /usr/include/pgsql/server "email.c"
gcc -g -shared -fPIC -o "emaildt.so" email.o
which library I have to
Hi all,
strange errors with a empty table:
kalman=# create table test();
CREATE TABLE
kalman=# select * from test t union select * from test t1;
ERROR: invalid memory alloc request size 0
I think this have to return:
--
(0 rows)
Regards
Gaetano Mendola
---(end of
cc email.c -I. -I /usr/include/pgsql/server
I seen also that a library called libpgext.so
is created.
Shall I do the same ? Are guide line to use out there?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Conway wrote:
| On Sat, 2004-05-08 at 13:10, Gaetano Mendola wrote:
|
|>However an *add on* is an *add on* with not the same eligibility
|>of the main project
|
|
| I'd suggest implementing the custom datatype first and packaging it
|
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Can't you do what you want as a local add-on?
I guess that for manage efficiently million of email addresses I need
to have a built in type instead of a domain with a regex as validator,
You probably
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
about you is it ok for you if I write the email built in type ?
You're going to have to explain why it has to be a built-in type.
Can't you do what you want as a local add-on? Is it likely that
the functionality
choose one ot other one, and basic all why
drop index idx_my_index cascade;
doesn't drop the constraint too?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-noma
Hi all,
about you is it ok for you if I write the email built in type ?
I know of course that I can do it with a DOMAIN.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http
inserted in the file
at point 1
and what else ? For example how may I define the name for my new type ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
that programmers are not aware of
( see select max(id) from foo; optimized with a order by + limit 1 ).
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
pgsql 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.
my two cents.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Hav
developers :-o
You should really get the CVS code if you want to hack on Postgres ...
there are a lot of changes since 7.4.3.
7.4.3 is not out yet, even I don't find the TAG on CVS.
Regards
Gaetano Mendola
---(end of broadcast)---
ot;id_code_pool");
or
ALTER TABLE activation_code ADD UNIQUE ( code, id_code_pool );
with \d command there is no difference but is different because the first command
create an index deleteable with a "drop index".
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
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 Me
is not so expensive after all.
Please, don't consider optimization that other DBMS are performing will
be good also for postgres, I think Oracle made pre forking of a pool of
process and this because a Oracle process when is forked do more work
then a postmaster.
Regards
Gaetano Mendola
-
de a table definition
could save us some pains.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
r,
fault tollerance, load balancer, ... ) ?
I'm looking forward to these tools indeed.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Tom Lane wrote:
I was able to reproduce the crash but not the hang. Would you see if
the attached patch fixes both symptoms on your machine?
Yes, problem gone.
I discover however that what I was believing an hang was in reality
just a delayed crash.
Regards
Gaetano Mendola
; shutdown TRUE
LOG: next transaction ID: 195700; next OID: 5718523
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: record with zero length at 0/4877FD78
LOG: redo is not required
LOG: database system is ready
Regards
Gaetano Mendola
Jürgen Cappel wrote:
Point 1 I completely agree on: byte order, alignment, padding, etc.
is different for each platform and data cannot directly be exchanged.
Point 2: who really needs C++ ??
We use it, a multi path TCP router written in C++ and behind
there is a Postgresql...
Regards
Gaetano
t;- Idle in transaction
6) select now();|select now();
~| <- Idle in transaction
7) rollback;|rollback;
~| <- Connection Idle
AS you can see the JDBC driver must do a begin only before the
first statement.
Am I missin
Do you know if postgres made assumption on the
access time time stamp for the files on his
own file sistem ? If not I'm wondering if
mount a partition with the option "anotime"
can improve the disk i/o performance.
Regards
Gaetano Mendola
---(e
Tom Lane wrote:
Red Hat's still shipping 2.5.4a according to a quick look...
Well Red Hat's still ship Postgres 7.3.4 ...
I'm not considering anymore RH to be up to date with various versions
:-(
Gaetano
---(end of broadcast)---
TIP 9: the planner
7.3.4 just because the guys on the operational side
install only precompiled pachage :-(
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
raise a warning if the old GUC is used, can speed the
adoption of new GUCs variables.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
slru.c had had less-paranoid error checking.
[SNIP]
Clap. Clap.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Tom Lane wrote:
Comments?
Really ugly but effective.
Is ABS enough on a 64-bit architecture ?
Or is better use labs ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
d be great. I still have a RH 6.2 machine in
case anybody still wants that.
I'll do it tomorrow, or is may be better do it for the 7.4.1 ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send
0-0.2
version!
I'm able to put my hand on RH 8.0, RH 9.0, RHAS 2.1 and RHAS 3.0
and RH 7.3 systems, if you need some help let me know.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an a
Tom Lane wrote:
I have committed a fix into 7.5devel to do this properly. I think this
is the last case wherein btree is unnecessarily inefficient for large
numbers of equal keys.
Any chance to have it on 7.4.1 ?
Regards
Gaetano Mendola
---(end of broadcast
http://www.semantics.org/tyr/tyr0_5/list.h
=
In this way we are going to save a pointer for each node,
what do you think ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Lamar Owen wrote:
On Tuesday 02 December 2003 06:29 pm, Gaetano Mendola wrote:
Lamar Owen wrote:
You need to specify that you are building for Red Hat 9 on the command
I'll try.
Ok.
I did it on a RHAS 2.1
and I get:
make[3]: Leaving directory `/usr/src/redhat/BUILD/postgresql-7.4/s
Lamar Owen wrote:
On Monday 01 December 2003 08:53 pm, Gaetano Mendola wrote:
Hi all,
I'm still experiencing problem trying to
rebuild the rpm from the file:
postgresql-7.4-0.5PGDG.src.rpm
I seen that the configure is done with:
--with-krb5=/usr.
You need to specify that you are buildin
krb5-devel-1.2.7-10
krb5-libs-1.2.7-14
krb5-workstation-1.2.7-14
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
with file from package
unixODBC-devel-2.2.3-6
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
unt(*) information in a special table,
why not implement the same in a way "builded in" ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
You may need to add explicit typecasts
now return a timestamp with time zone and your function
take a timestamp without time zone.
^^^
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 8: explain analyze is your friend
le to apply it also to a 7.3.X ( our production
DB).
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Verbus Counts wrote:
{/opt/postgres/postgresql-7.4RC1}$ ll core
-rw--- 1 postgres postgres726684 Nov 6 10:55 core
Can you show us the stack trace ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'ki
Who is eligible to be a "contributor" ?
Who wrote a single line of code that now is inside Postgres?
Who discovered a "major" bug ?
Who partecipate actively to all discussions ?
Regards
Gaetano Mendola
---(end of broadcast)--
Alvaro Herrera wrote:
On Tue, Nov 04, 2003 at 05:35:42PM +0100, Gaetano Mendola wrote:
I agree in general with you for these "general" arguments, but here we
are talking about to introduce a sleep ( removable by guc ) or not! What
about the hash refactoring introduced with 7.4? Are
Jan Wieck wrote:
Gaetano Mendola wrote:
Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Tue, 4 Nov 2003, Gaetano Mendola wrote:
Is in the last Tom's patch about Vacuum sleep between pages ?
that won't be in v7.4, to the best of my knowledge ...
Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Tue, 4 Nov 2003, Gaetano Mendola wrote:
Is in the last Tom's patch about Vacuum sleep between pages ?
that won't be in v7.4, to the best of my knowledge ...
Definitely not. It's a very experim
Marc G. Fournier wrote:
As Tom announced on Friday, Release Candidate 1 has now been tag'd and
bundled ... please test to confirm that nothing seems off with this build
Is in the last Tom's patch about Vacuum sleep between pages ?
Regards
Gaetano Mendola
nly to any recent
7.4 beta. You could likely adapt it to 7.3 without much effort.
Will we have this on 7.4 ?
I tried it and improve a lot the responsiness of my queries just putting
the delay equal to 10 ms.
Regards
Gaetano Mendola
---(end of broadcast)---
in a
> transaction under the SQL standard is START TRANSACTION.
These IMHO means push people to not use BEGIN anymore.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nom
Bruce Momjian wrote:
I can confirm this bug in CVS.
Something is cached, if you quit your psql session after
droping the constraint, and you start another psql session
the problem disappear.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 2
Hi all,
why START TRANSACTION READ ONLY is allowed
and not BEGIN READ ONLY ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Bruce Momjian wrote:
I think you are pointing to the wrong version --- I see:
LOG: duration: 0.998 ms statement: select 1;
I'm a dummy, I forgot to do gmake install
after have compiled the last beta :-(
yes you're right.
Regards
Gaetano Mendola
I'm seeing on the log file:
LOG: duration: 0.024814 select now();
Am I wrong or we agree to have:
LOG: duration: 24.81 ms select now();
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list arc
ount(*) ) ?
Why not do a sort of "vacuum" if a scan table happen ( during a simple
select that invole a full scan table for example )?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
nd a way to calculate this elbow ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Gaetano Mendola wrote:
Hi all,
I'm importing on Postgres 7.3.4 a dump and after one hour
the process is still there to perform a COPY of a table with about
~1.5M rows.
BTW after 2 days the process is still importing :-(
Gaetano
---(end of broa
2 68
2 0 0 407940 21584 125640 47097600 0 0 524 509
29 2 69
1 0 0 407940 21584 125640 47097640 4 0 630 634
30 1 69
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched ou
uot;)
may be here deleteThreshold shall be AnalyzeThreshold and
insertThreshold shall be VacuumThreshold
am I missing something?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please
Andreas Pflug wrote:
Gaetano Mendola wrote:
Right, anyway there was typos in the translation, and my vi was unable
to display: è, à. Anyway is a common stuff and well accepted have a'
instead of à.
Hi Gaetano,
in the era of unicode I don't quite see why this needs to be
accep
Andreas Pflug wrote:
Gaetano Mendola wrote:
Peter Eisentraut wrote:
Gaetano Mendola writes:
Some corrections.
I don't understand why your patch changes è to e' and à to a'. Also,
please make your next patch so that it can be applied to the file it.po
(not psql.pot).
Be
Peter Eisentraut wrote:
Gaetano Mendola writes:
Some corrections.
I don't understand why your patch changes è to e' and à to a'. Also,
please make your next patch so that it can be applied to the file it.po
(not psql.pot).
Because with some terminal the character è, à, and o
tions.
Regards
Gaetano Mendola
psql.pot.patch.gz
Description: GNU Zip compressed data
---(end of broadcast)---
TIP 8: explain analyze is your friend
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
e nice have this kind of "NOTICE", that may be is better call
"INTERNALS", and switchable off.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
dependend
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
r line 2
is the intended behaviour ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
function and see if is used inside a view or not,
and choose the right permission.
We have ~ 100 View and ~ 100 functions :-(
Regards
Gaetano Mendola
PS: I vote that is a bug :-)
---(end of broadcast)---
TIP 6: Have you searched our list
[EMAIL PROTECTED] wrote:
2. SELECT d_next_o_id
INTO current_o_id
FROM district
WHERE d_w_id = 1
AND d_id = 8
3. UPDATE district
SET d_next_o_id = d_next_o_id + 1
WHERE d_w_id = 1
AND d_id = 8
I don't know exactly what you are trying to do
but usualy in cases like this, in ord
Hiroshi Inoue wrote:
Gaetano Mendola [mailto:[EMAIL PROTECTED] wrote:
Hiroshi Inoue wrote:
instead. Because it was impossible to make REINDEX transaction-safe
then, such flag was needed to suppress inconsistency as less
as possible.
This mean that the actual REINDEX is not transaction-safe
Hiroshi Inoue wrote:
> instead. Because it was impossible to make REINDEX transaction-safe
> then, such flag was needed to suppress inconsistency as less
> as possible.
This mean that the actual REINDEX is not transaction-safe ?
Regards
Gaetano Mendola
-
Peter Eisentraut wrote:
"transaction block" vs. "BEGIN/END transaction block" -> Both are used, I
think the first one is better.
I vote for the second one.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't
Tom Lane wrote:
Your idea of reducing id_provider to id_class using a separate query
seems like a good one to me --- that will allow the planner to generate
different plans depending on which id_class value is involved.
However is not a natural way to approch the problem;
Am I wrong ?
Gaetano
Joshua D. Drake wrote:
I need a hug.
*HUG*
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
The select take long:
Postgres7.3.3: average 4000 ms
Postgres7.4b2: average 2600 ms
you can experiment your self with the dump that I gave you
Hm. I tried to duplicate your results. I'm getting about 5400 msec
versu
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Hm, it sure looks to be exactly the same plan. The performance
difference seems to be just that the seqscans are faster. I surmise
that in the 7.3 database you had a lot of dead rows, or at least a lot
of free
Gaetano Mendola wrote:
Tom Lane wrote:
Hm, it sure looks to be exactly the same plan. The performance
difference seems to be just that the seqscans are faster. I surmise
that in the 7.3 database you had a lot of dead rows, or at least a lot
of free space. Possibly you need to vacuum more often
of junk in the tables.
The two databases were created from scratch and the first
operation on it ( after a vacuum analyze ) was just that query.
I will try to pump up the statistic target.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have
3 msec
(11 rows)
How you can see with 7.4 the two queries ( the original with the join
and with the IN nested ) are performing at the same way.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
m kinda leaning
towards the first; does anyone feel that it's a valuable feature to keep?
My vote is for remove this feature.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
;s why they need to
> >invent combination operations like MODIFY CONSTRAINT.
>
> As my colleague says:
>
> it is indeed a lazy choice, but super safe and that's the goal.
Does your colleague know the Aesops's Fables: "The fox and the Grapes" ?
Regards
Gaetano Mendol
it sure sounds like a bug. What logic is there that table access
> use the view permissions, but not function access? Could we just use
> SECURITY DEFINER for function calls in views?
I already had this problem, look here:
http://groups.google.it/groups?q=postgres+security+de
it sure sounds like a bug. What logic is there that table access
> use the view permissions, but not function access? Could we just use
> SECURITY DEFINER for function calls in views?
I already had this problem, look here:
http://groups.google.it/groups?q=postgres+security+de
301 - 400 of 418 matches
Mail list logo
