having the correct
> updated values.
> We are using default isolation level (Read Committed)
PostgreSQL 8.1 has been unsupported since 2010. Once you've upgraded
to a supported version, if the problem persists, we may be able to
help.
Cheers,
David.
--
David Fetter http://fetter.org/
On Mon, Jun 11, 2012 at 06:21:43PM +0200, Magnus Hagander wrote:
> On Mon, Jun 11, 2012 at 6:14 PM, David Fetter wrote:
> > On Mon, Jun 11, 2012 at 06:04:22PM +0200, Magnus Hagander wrote:
> >> On Mon, Jun 11, 2012 at 6:01 PM, David Fetter wrote:
> >> > On Mon, Ju
On Mon, Jun 11, 2012 at 06:04:22PM +0200, Magnus Hagander wrote:
> On Mon, Jun 11, 2012 at 6:01 PM, David Fetter wrote:
> > On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
> >> On Mon, Jun 11, 2012 at 5:14 PM, wrote:
> >> > The following bug
On Mon, Jun 11, 2012 at 05:51:06PM +0200, Magnus Hagander wrote:
> On Mon, Jun 11, 2012 at 5:14 PM, wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 6687
> > Logged by: David Fetter
> > Email address: da...@
ber-0-for-toast-value-96635-in-pg-toast-2619-tp5682176p5682273.html
> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mail
h, so please to report bugs in that
language, enlisting help wherever you need to in order to do so.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
iCal: webcal://www.tripit.com/feed/i
o much for copying from a separate file.
>
> The attached patch seems like an appropriate fix. However, I'm
> unsure whether to apply it to released branches ... does anyone
> think this might break somebody's application?
No.
Cheers,
David.
--
David Fetter http://fe
The following bug has been logged online:
Bug reference: 6067
Logged by: David Fetter
Email address: dfet...@vmware.com
PostgreSQL version: 9.0.4
Operating system: Linux
Description:In PL/pgsql, EXISTS(SELECT ... INTO...) fails
Details:
Here's some example
at :)
> but the second case seems seriously annoying, since there's no way
> for someone to write a CTE-containing rule action without risking a
> conflict. Ideas anybody?
Is there some way to throw "not implemented" there, too? It seems to
me that making accommodations for
some kind of plans to build major version
upgrades into your development process, as end-of-life is a fact of
life in this as in every other software or system.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter
On Mon, Nov 15, 2010 at 06:55:47PM -0500, Tom Lane wrote:
> "David Fetter" writes:
> > CREATE SEQUENCE my_seq;
> > WITH t AS (SELECT nextval('my_seq')) VALUES(1);
> > SELECT currval('my_seq');
>
> > ERROR: currval of sequence &
The following bug has been logged online:
Bug reference: 5754
Logged by: David Fetter
Email address: da...@fetter.org
PostgreSQL version: 8.4+
Operating system: All
Description:CTE optimization fails to account for side effects
Details:
Here's how to repr
d.
> >
> Thanks, I will do that. However, I cannot call myself a hacker, I
> am but a mere beginner with Postgres.
You're a hacker when you start hacking :)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfet
gates, or at least never have any built-in ones
> that use such a feature.
>
> By my count the following people had offered an opinion on making
> this change:
> for: tgl, josh, badalex, mmoncure
> against: rhaas, thom
> Anybody else want to vote, or change their
;) People who have been
> waiting for this will burn me as a heretical witch... er.. man
> witch... warlock?
Witch.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
iCal: webcal://
>
> Even if we quote them in the dump, I assume applications would need
> to quote them too, which I doubt many do.
It seems like something that's doable by pg_dump as a "default off"
option. TODO for 9.1?
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415
read? I may have inadvertently used some
> bash/gnu-isms... sorry about that.
>
> *** a/configure
> --- b/configure
Edit configure.in, not configure :)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: dav
t report them here; please report to those
> projects directly. Alternatively you can look at the available href='/community/lists'>mailing lists and see if there is a more
> apropriate list available."
This is better than what I sent :)
Cheers,
David.
--
David Fetter http
oblems with
the PostgreSQL database, for problems with database connectors like
JDBC and ODBC, graphical administration tools like pgAdmin and
phpPgAdmin, or other external projects like Slony, Bucardo, etc.,
please report to them directly. In cases where you have a problem
with things outside
braic numbers, of which rational numbers are a proper
subset, is countable and hence has Lebesgue measure zero on the real
line.
;)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
On Fri, Oct 16, 2009 at 01:28:57PM -0400, Tom Lane wrote:
> David Fetter writes:
> > I think what the OP was expecting was to have the last value be 3
> > instead of changing. This is at least a POLA violation.
>
> [ shrug... ] It's what the spec requires, as far
have the last value be 3
instead of changing. This is at least a POLA violation.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
Remember to vote!
Consider donating to Postgres: http://
ts there... We're probably just back in the situation where
> we need more moderators for it...
I'd be happy to be added as moderator for -bugs or any other list that
needs love. I already do -general and sfpug, so this shouldn't be
much extra work :)
Cheers,
David.
--
David Fe
On Mon, Sep 21, 2009 at 02:28:11PM -0400, Robert Haas wrote:
> On Mon, Sep 21, 2009 at 2:17 PM, David Fetter wrote:
> > On Mon, Sep 21, 2009 at 01:06:17PM -0400, Alvaro Herrera wrote:
> >> David Fetter escribió:
> >> > On Mon, Sep 21, 2009 at 12:06:30PM -0400, Alvaro
On Mon, Sep 21, 2009 at 01:06:17PM -0400, Alvaro Herrera wrote:
> David Fetter escribió:
> > On Mon, Sep 21, 2009 at 12:06:30PM -0400, Alvaro Herrera wrote:
> > > David Fetter escribió:
> > >
> > > > Taken literally, that would mean, "the last acti
On Mon, Sep 21, 2009 at 12:06:30PM -0400, Alvaro Herrera wrote:
> David Fetter escribió:
>
> > Taken literally, that would mean, "the last action before the
> > backend exits," but at least to me, that sounds troubling for the
> > same reasons that "end of
for the same reasons
that "end of transaction" triggers do. What happens when there are
two different END blocks in a session? With connection poolers,
backends can last quite awhile. Is it OK for the END block to run
hours after the rest of the code?
Cheers,
David.
--
David Fet
uniqueness, and
only that. If you wish to create some entity which has some other
properties, be aware that such entities require locking, which sharply
limits their speed.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidf
the file, but the whole question of date and time handling
has been tricky and complicated for all of human history.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
Remember to vot
fixing coding mistakes in formatting.c?
That depends on whether the project lasts forever ;)
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
Remember to vote!
Consider donating to Postgres
iant than MySQL,
> but Postgres is not 100% compliant either. Is any database system
> 100% compliant?
No.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECT
gs@postgresql.org)
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-bugs
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/ERROR%3A--unexpected-data-beyond-EOF-in-block-X-of-relation-%22file%22-tp1968
t I don't think it is.
Delphi's memo type corresponds (roughly) to PostgreSQL's TEXT/VARCHAR
one, so it's your expectations that were off.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfett
g isn't a bug unless you can reproduce it on the latest
minor version, in this case 8.3.3, of the major version, in this case
8.3, that the bug appears in.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype:
;
This is a bug. Extract(epoch from [timestamp without time zone])
shouldn't work at all. Epoch only has meaning in the context of a
timestamptz.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: df
ng.
> For example, in Oracle all works propertly, and result of SELECT is:
> SQL> select * from n;
>
> N
> --
> 2
> 3
> 4
You can get around this by doing:
UPDATE t
SET n=t.n+1
FROM (
SELECT n FROM t ORDER BY n DESC
) t
2 X
>
> Now, we update table A with values from temporary table temp_A doing
> something like
>
> UPDATE "A" SET "Name" = "temp_A"."Name" FROM "temp_A" WHERE "A".record_id =
> "temp_A".record_id
ou don't know whether they
will be NULL when you write the SQL, use constructs like
WHERE foo IS NOT DISTINCT FROM $1
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTE
t you need
to do.
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: [EMAIL PROTECTED]
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
---
G is only supported at the top level of a query.
What would be involved with making this possible? What we have at the
moment is a pretty clear POLA violation because unlike the rest of the
row-returning objects (tables, views, SRFs and VALUES() clauses), only
RETURNING can't be used in a sub
ded.
There's a setting you can set in your postgresql.conf that will help
you find these problems more automatically:
custom_variable_classes = 'plperl'
plperl.use_strict = true
Cheers,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778
m: linux
> Description:Linux/M32R project
> Details:
>
> Developing Linux/M32R.
Inoaka-san,
Please consider submitting this as a pgfoundry project or as a porting
issue on the pgsql-hackers mailing list.
Regards,
David.
--
David Fetter <[EMAIL PROTECTED]> http://fet
ixed
> * someday, but for now, punt.
> */
>
> It's in the analyze.c code, but not in the docs.
Should a doc patch be in the offing here?
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
On Mon, Oct 16, 2006 at 10:00:13AM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > 1. We can continue to support 5.6 until we can't any more, and
> > statistically speaking that "can't any more" is quite likely to
> > happen
On Mon, Oct 16, 2006 at 12:10:42AM -0400, Bruce Momjian wrote:
> David Fetter wrote:
> > On Sun, Oct 15, 2006 at 07:07:18PM -0400, Tom Lane wrote:
> > > David Fetter <[EMAIL PROTECTED]> writes:
> > > > At some point, we will find something where we will have to
On Sun, Oct 15, 2006 at 07:07:18PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > At some point, we will find something where we will have to duplicate
> > some large hunk of 5.8's functionality to support 5.6.
>
> No, we won't; we a
On Sun, Oct 15, 2006 at 06:12:43PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Sun, Oct 15, 2006 at 04:43:17PM -0400, Tom Lane wrote:
> >> ISTM the real question is what do we buy if we make such a
> >> restriction? Getting rid of a f
ck is mighty ugly.
>
> I am also wondering, now that it's been raised, if we need to issue
> a "use utf8;" in the startup code, so that literals in the code get
> the right encoding.
That would be a reason to go to 5.8, as 'use utf8;' is tricky at best
in 5.6.
Cheer
On Sun, Oct 15, 2006 at 04:43:17PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > I'd like to suggest that raise that minimum requirement for Perl
> > to 5.8 for 8.3, as Perl 5.8 will be about five years old by then.
>
> Well, we're s
system or other so ancient that Perl 5.8 did not come pre-installed
with it, but we can't be supporting other projects backwards into
eternity. Supporting our own is already plenty of work.
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
phone: +1
On Thu, Aug 10, 2006 at 11:44:31AM -0700, Jie Liang wrote:
> Tom,
> I used:
> pg_dumpall > db.out on my 7.4.2 server
It's not a bug. Use the pg_dumpall from 8.1.4 to talk to the
still-live 7.4.2 server :)
Cheers,
D
--
David Fetter <[EMAIL PROTECTED]> http://fetter.org/
On Thu, Jul 20, 2006 at 10:46:27PM -0400, Tom Lane wrote:
> "David Fetter" <[EMAIL PROTECTED]> writes:
> > is there some way to let the right hand side of SET be the (TEXT)
> > output of a function?
>
> No. SET is a utility command and utility commands gener
The following bug has been logged online:
Bug reference: 2542
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: All
Operating system: All
Description:ALTER USER foo SET bar = func(baz) errors out
Details:
foo=> ALTER USER foo
On Wed, Jul 19, 2006 at 07:02:15PM -0400, Tom Lane wrote:
> "David Fetter" <[EMAIL PROTECTED]> writes:
> > Description:PL/PgSQL doesn't disallow COPY commands on
> > compile, even though it disallows them.
>
> There are many many things that wo
The following bug has been logged online:
Bug reference: 2539
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: All
Operating system: Linux and OSX that I've tested
Description:PL/PgSQL doesn't disallow COPY commands on compile, e
On Tue, Jan 31, 2006 at 09:50:26PM -0600, Andrew Dunstan wrote:
> David Fetter said:
> > On Tue, Jan 31, 2006 at 08:03:41PM -0500, Bruce Momjian wrote:
> >> Uh, couldn't the delimiter be a backslash in CVS mode?
> >
> > I don't think so. Folks?
>
>
cstate->null_print, cstate->delim[0]) != NULL)
ereport(ERROR,
(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
errmsg("COPY delimiter must not appear in the NULL
specification")));
I suppose that a different error code might be The Right Thing⢠here.
On Mon, Jan 30, 2006 at 08:21:34AM -0500, Andrew Dunstan wrote:
>
>
> David Fetter wrote:
>
> >
> >+/* Disallow BADCHARS characters */
> >+if (strcspn(cstate->delim, BADCHARS) != 1)
> >+ereport(ERROR,
> >+
On Sun, Jan 29, 2006 at 10:20:47PM -0500, Neil Conway wrote:
> On Sun, 2006-01-29 at 17:03 -0800, David Fetter wrote:
> > Another followup, this time with the comment done right.
>
> + /* Disallow the forbidden_delimiter strings */
> + if (strcspn(cstate->
On Sun, Jan 29, 2006 at 04:41:43PM -0800, David Fetter wrote:
> On Sun, Jan 29, 2006 at 09:50:08PM +0000, David Fetter wrote:
> >
> > The following bug has been logged online:
> >
> > Bug reference: 2221
> > Logged by: David Fetter
> &g
On Sun, Jan 29, 2006 at 09:50:08PM +, David Fetter wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2221
> Logged by: David Fetter
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: all
> Operating system: all
&
The following bug has been logged online:
Bug reference: 2221
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: all
Operating system: all
Description:Bad delimiters allowed in COPY ... TO
Details:
This came up while I was testing my
mmitted your patches to current and 8.1 stable.
Please apply the following patch that removes an unneeded (and broken)
counter increment.
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 415 235 3778
Remember to
Folks,
Having blank lines in -f scripts was causing silent failures. This
fixes it, for some value of "fixes." If it's OK, please apply to 8.1
CURRENT and CVS TIP :)
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 415 235 3778
Remember to vote!
Index:
On Tue, Nov 22, 2005 at 06:20:37PM -0500, Bruce Momjian wrote:
>
> TODO has:
>
> o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
Great :)
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 415 235 3778
Remember to vote!
---
On Thu, Nov 17, 2005 at 07:11:42PM -0500, Neil Conway wrote:
> On Thu, 2005-11-17 at 13:07 -0800, David Fetter wrote:
> > This is still a bug, or at least a big gotcha.
>
> It's not a bug, merely an unimplemented feature. If no one beats me
> to it I'll take
On Thu, Nov 17, 2005 at 05:32:43PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Thu, Nov 17, 2005 at 04:37:14PM -0500, Tom Lane wrote:
> >> CREATE TEMP TABLE foo ... ON COMMIT DROP;
>
> > It's that first little elipsis mark that&
On Thu, Nov 17, 2005 at 04:37:14PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > This is still a bug,
>
> No, it's a feature request, and a rather low-priority one considering
> you can already do
>
> CREATE TEMP TABLE foo ... ON C
On Thu, Nov 17, 2005 at 03:26:21PM -0500, Jaime Casanova wrote:
> On 11/17/05, David Fetter <[EMAIL PROTECTED]> wrote:
> >
> > The following bug has been logged online:
> >
> > Bug reference: 2051
> > Logged by: David Fetter
> > Email a
The following bug has been logged online:
Bug reference: 2051
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0x
Operating system: Linux
Description:CREATE TEMP TABLE AS SELECT doesn't play nice with ON
COMMIT DROP
Details:
C
s not seem to have a method of accepting enhancement
> requests. That is why I specifically put ENHANCEMENT REQUEST in the
> description.
I've never seen somebody try so hard to get himself labeled as a
help-rejecting complainer before. Are you *certain* that this is what
you want to do,
f compatibility.
This is not one of those cases.
> Are you honestly going to tell me that if your user base requested
> certain additional functionality that you would refuse to include it
> simply because it was "not in the standard"?
Several proposals have been rejected because
that you must support multiple back-end
databases, please look over this presentation
http://www.powerpostgresql.com/Downloads/database_depends_public.swf
and see whether this is really a road you want to travel.
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org
r they are equal, and
so the only right answer to "Is BogDan's birthday unequal to his
coworker's?" is "I don't know."
HTH :)
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vo
for a fix in 8.2, but for now, use another PL like PL/Perl, or (if
you're brave ;) C.
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
---(end of broadcast)---
TI
in this case that the parameter names of the function
> cannot be the same as the column names used by the INSERT statement
> -- clashes.
This is not really a bug. If the things really are different, in this
case function input parameters and column names, they should also have
differen
ith
> > previous versions of PostgreSQL.
> >
>
> I am working on a patch to warn on psql startup if the backslash
> commands might not work.
In case of relenting on the feature freeze vs. bug thing, I am
preparing a patch that makes psql's \d commands backward-compati
The following bug has been logged online:
Bug reference: 1770
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux
Description:Composite type dependency broken
Details:
Here's a repro (psql):
create tabl
Folks,
Pardon the dup, but I couldn't post via the web site :/
The following bug has been logged online:
Bug reference: 1770
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux
Description:Composite
e-10
> digits. I once had a clue about the exact laws for this, but it was
> many years ago :-(
As with base-10, any denominator that can't be expressed as a power of
the prime factors in the base results in a repeating number. So
basically any denominator that can't be express
On Sun, Sep 26, 2004 at 11:45:42PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > CREATE OR REPLACE FUNCTION has_bad_chars(text) RETURNS BOOLEAN
> > AS $function$
> > SELECT $1 ~ $q$[\t\r\n\v|$qq$\$qq$]$q$;
> > $function$ LANGUAGE SQL;
tion.
Are you going to support your own branch of PostgreSQL in perpetuity?
That's what you're signing up for if you don't upgrade.
> so.. is there a way to fix this without upgrading postgres, but not
> using Redhat 7.x ?
No.
Cheers,
D
--
David Fetter [EMAIL PROTECTED]
On Fri, Aug 06, 2004 at 01:32:32PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > Here's a symptom as reported by John Hansen aka applejack:
>
> > SELECT 'r'||'\000\125'||'hello' ~ '^.hello' AS "OM
Kind people,
Here's a symptom as reported by John Hansen aka applejack:
SELECT 'r'||'\000\125'||'hello' ~ '^.hello' AS "OMG";
OMG
-
t
(1 row)
I have produced this behavior in 7.4.3 and CVS tip.
This should be false, shouldn&#
7; ~ '\\d');
?column?
--
t
(1 row)
test=> select ('123' ~ '\d');
?column?
--
f
(1 row)
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 510 893 6100cell: +1 415 235 3778
Not believin
Tom Lane <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (David Fetter) writes:
>> I've written a little hack, here included, which is supposed to find
>> whether a user is in a group. I'd intended to do a PERFORM instead of
>> SELECT INTO, but PERFORM appear
r u
, pg_group g
WHERE
u.usename = the_user
AND g.groname = the_group
AND u.usesysid = ANY (g.grolist);
IF FOUND
THEN
RETURN true;
ELSE
RETURN false;
END IF;
END;
' LANGUAGE 'plpgsql' STRICT IMMUTABLE;
TIA for any hints, tips
87 matches
Mail list logo
