.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
test with
very short checkpoint intervals. Something like 30s. Just to make sure that
the logic is all correct and unexpected things don't start happening.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
able to connect to a postgres server shouldn't mean being able to open
tcp connections *from* that server to arbitrary other host/ports. Consider for
example that it would allow a user to perform a port scan from inside your
network to see what internal services are running.
--
Gregory Stark
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get
they create any function using an
untrusted language.
And the author of the script here is not being careful in this respect. The
sysadmin isn't the one writing the create function statement.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end
the same concerns arise and the same conclusion reached.
That users should be granted permission to execute it based on local policies.
Certainly granting execute permission to public by default is a bad start in
that regard.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
the
security model by merely being installed then programmers or dependent modules
can request packages and dbas can be confident that installing them won't
introduce security holes. Isn't that a property software should have even if
it's just an add-on module?
--
Gregory Stark
EnterpriseDB
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get
have multiple
users. All I'm suggesting is that the default install script should just do
that rather than do something that the docs will then recommend you undo.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
a way to make this work usefully.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED
, but it has
no other user visible behavior.
On the other hand what happens if you have constraints not deferred, insert a
record, then set constraints deferred and update it?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
Gregory Stark [EMAIL PROTECTED] writes:
On the other hand what happens if you have constraints not deferred, insert a
record, then set constraints deferred and update it?
After having a coffee this is obviously not a problem since if you have
constraints not deferred then the constraint
Uhm, this is a one-line *bug fix*.
Bruce Momjian [EMAIL PROTECTED] writes:
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Gregory Stark wrote:
pgbench's
really necessary. My fix does resolve the only actual documented
inaccuracy in the existing method.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Yeah. I was basically waiting to see if anyone could come up with a
faster solution. Since no one seems to have an idea how to do it
better, I'm inclined to apply the patch for 8.3
calculate the precision to be precisely enough to maintain the original
precision. Ie, /1000 should just give you n.nnn not n.nnn and more
importantly it should never round.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
Tatsuo Ishii [EMAIL PROTECTED] writes:
Can someone enligten me what the usecase for CREATE TABLE LIKE at this
moment is?
One of the main use cases I envision is wanting to create new partitions
suitable for being added to a partitioned table.
--
Gregory Stark
EnterpriseDB http
Jim C. Nasby [EMAIL PROTECTED] writes:
On Fri, Jul 20, 2007 at 12:40:46PM +0100, Gregory Stark wrote:
One of the main use cases I envision is wanting to create new partitions
suitable for being added to a partitioned table.
Except that's normally done with CREATE TABLE INHERITS, which
with async
commits or with something like commit_delay and some extra logic in the
walwriter to aim for grouping together the maximum number of commits.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
.
*/
/*#define HAS_GETPGRP2 / **/
/* HAS_GETPPID:
* This symbol, if defined, indicates that the getppid routine is
* available to get the parent process ID.
*/
#define HAS_GETPPID /**/
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
the
config.h file themselves and they missed this detail.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Without async commits? Do we really want the walwriter doing the
majority of the wal-flushing work for normal commits? It seems like
that's not going to be any advantage over just having some random
backend do
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Magnus Hagander [EMAIL PROTECTED] writes:
Stefan mentioned that the warning may be one that shows up in a different
compiler somewhere as well, thouh, which might indicate that we should fix
the underlying issue
but the related transaction commit is lost
then you have a problem.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
there's no way to include it (if it needs quoting) but only when you specify
it this way.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
,/* Stop history lookup if a match of 128 bytes is found */
! 6 /* Look harder for a good match. */
};
const PGLZ_Strategy * const PGLZ_strategy_always = strategy_always_data;
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Decibel! [EMAIL PROTECTED] writes:
On Fri, Jul 27, 2007 at 04:07:01PM +0100, Gregory Stark wrote:
Fwiw, do we really not want to compress anything smaller than 256 bytes
(everyone in Postgres uses the default strategy, not the always strategy).
Is there actually a way to specify always
documenting it on the comparison operators page -- the only page
where it seems it would make sense -- would be a bad idea.
pg_convert_to_scalar.patch.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Attached is a patch which implements, as discussed briefly on -hackers, a
user-visible function to get at the information that convert_to_scalar uses
to
generate selectivity estimates.
This is an astonishingly bad
are used to ensure that no transaction for which
the older tuples are visible can use the index.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
wonder if it makes more sense to make this an optional btree
operator class support procedure rather than a type function.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
When complaining I hadn't read the pghackers thread in which you
suggested this, and now that I'm caught up on email I remain
unconvinced. What do you need convert_to_scalar
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
How so? The entries in the histogram are equidistant by definition.
Huh? They have equal number of values between them, they're not equidistant
in
the scalar space. So the area
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
I was planning to use the first and last histogram values for the frame of
reference. It could still produce some weird graphs but those cases are
precisely the cases where users
the timestamps in the appropriate timezone for user's consumption.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
be parsed by anything.
But perhaps I overestimate Excel's abilities.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
I don't think it's an acceptable change in either place. People who
want to see UTC in their logs can start the postmaster in UTC. Those
who are accustomed to seeing local time
Decibel! [EMAIL PROTECTED] writes:
On Sun, Jul 29, 2007 at 12:06:50PM +0100, Gregory Stark wrote:
You would have to recompile with the value at line 214 of
src/backend/utils/adt/pg_lzcompress.c set to a lower value.
Doesn't seem to be working for me, even in the case of a table with a
bunch
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
The scenario I was describing was having, for example, 20 fields each
of which are char(100) and store 'x' (which are padded with 99
spaces). So the row is 2k but the fields are highly compressible, but
shorter than
effective. They
require a static dictionary but then that's precisely what I'm thinking of.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
would like to see all the data types in a file in adt. Even if it's
just a single file containing mostly just glue functions into code in
sc/backend/tsearch.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
declaring that the tid might sometimes not change after an
update.
Not sure what this translates to for MaxHeapTuplesPerPage though.
The rest I know less about and will leave to Pavan and Heikki (or anyone else
who was following those details more closely).
--
Gregory Stark
EnterpriseDB
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
Pavan Deolasee [EMAIL PROTECTED] writes:
Please see the version 14 of HOT patch attached.
I expected to find either a large new README, or some pretty substantial
additions to existing README files, to document how
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
);
+ state-boundUsed = true;
state-status = TSS_BOUNDED;
}
@@ -2284,7 +2285,6 @@
REVERSEDIRECTION(state);
state-status = TSS_SORTEDINMEM;
- state-boundUsed = true;
}
/*
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
? Corrections?
You should also take the appendix to Heikki's README about CREATE INDEX that I
wrote.
I plan to put this in src/backend/access/heap/README.HOT.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
are using old snapshots if we can
be sure they can't use the new plan then it would still be safe to use the
index in the new plan. Also in SERIALIZABLE mode those same statements hold
for temporary tables.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
. It seems an index lookup tries to prune a heap chain, and he
was asking if it should look at other chains on the page; I said not.
Whether the index lookup should prune the heap chain is another issue.
Pruning chains is kind of the whole point of the exercise no?
--
Gregory Stark
EnterpriseDB
already have the page pinned
yourself.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about
transactions to work, but on the
whole it seems at least as clean as the code we have now. Comments?
Just that it will be fascinating to see what effects this has on the
benchmarks.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
it unused).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do
aligned. So actually
it would never cross a hardware sector boundary.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe
the code will work of course) we should at a minimum be certain that the build
farm will detect the problem.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
This patch implements Florian's idea about how to manage snapshot xmax
without the ugly and performance-losing tactic of taking XidGenLock and
ProcArrayLock at the same time. I had
maintainers for modules of free software are often found anyways.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
, sizeof(TheLexeme), cmpLexemeQ);
if (res == NULL)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
changed, 5 insertions(+), 364 modifications(!)
packed-varlena-efficiency_v0.patch.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
database locks for user-visible operations which users
can drag out for long periods of time. (Not saying I agree with that design
but there are arguments for it and people do do it)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
;
- toast_sizes[i] = VARSIZE(toast_values[i]);
need_change = true;
need_free = true;
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support
-rd_rel-relkind == RELKIND_UNCATALOGED);
/*
* Get the tuple descriptor and break down the tuple(s) into fields.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
Testing Postgres with a small block size runs into an assertion failure when
it tries to toast a pg_proc tuple during initdb. I think the assertion is
just
wrong and RELKIND_UNCATALOGUED is valid here.
Uh, what
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
If I push the TOAST_TUPLES_PER_PAGE up to 16 I get another failure on the
same
line from trying to toast a sequence. If I add RELKIND_SEQUENCE to the
assertion then it passes all regression tests even if I push
likely to change and you
can always adjust the environment variable manually to fix the problem.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives
already fired its deadlock check before it was waiting directly on
autovacuum. But the only way I can see it happening is if another process is
cancelled before its deadlock check fires and the signals are processed out of
order. I'm not sure that's a case we really need to worry about.
--
Gregory
if multiple deadlock check signals fire for
the same autovacuum?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe
when the driver misinterprets the parameters.
I think it would be a very bad idea
to require that people use the function name in parameters,
I think were talking about only allowing it to disambiguate if the name is
shadowed by a variable in an inner scope.
--
Gregory Stark
EnterpriseDB
fields take more space and take longer to compare so to make consistent use of
resources you would want to avoid storing and comparing large numbers of them
whereas you could afford much larger targets for small quick columns.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Here's the WIP patch I described on -hackers to implemented ordered append
nodes.
merge-append-v1.diff.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
A trigger will probably beat a rule for inserts/updates involving a small
number of rows.
Which is exactly what partitioning is doing.
Say what?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
triggers over rules if only because rules
are just harder to understand. Arguably they don't really work properly for
this use anyways given what happens if you use volatile functions like
random() in your where clause.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
partitions should actually receive the updates and deletes.
I think triggers are the only solution for insert though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast
[]);
could be allowed if they could be contrived to introduce an assignment cast.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast)---
TIP 4: Have you
to
distinguish the dense areas from the sparse areas.
Perhaps something like starting with 1 bucket, splitting it into 2, seeing if
the distributions are similar in which case we stop. If not repeat for each
bucket.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
make me think you ran them but
just didn't show them though.
What about a merge join against an empty table? I suppose there would just be
no statistics?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support
data in there and have it be the UI's
responsibility to decide what data to display.
When that happens it would be nice to have the raw data used to generate the
cost estimations. At least the most important factors.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me
of it that's not going to help at all.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
so I don't have strong feelings
for this part either way.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast)---
TIP 3: Have you checked our
row ordering. This is a
pretty trivial patch, but seeing how late we are in the 8.3 release
cycle, I thought I'd better post it for comment anyway.
+1
I liked the synchronized_sequential_scans idea myself.
But otherwise, sure.
--
Gregory Stark
EnterpriseDB http
. It would be just another PL language to
load which can be installed like other ones. This could be a big advantage
because it doesn't look like there is a lot of support for putting th
obfuscation directly into the core code.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
for other applications like compiled
languages, though I think they would still want to save the source in prosrc
and the bytecode in probin.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training
.
In such a scheme I think you would put the key in an attribute of the
language. Either in pg_lang or some configuration location which the
obfuscate:plperl interpreter knows where to find.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's
stop some other country from coming up with the same idea of course
but we don't generally worry about what laws some hypothetical country might
introduce at some point in the future. That way lies madness.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about
for one.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
---(end of broadcast)---
TIP 6: explain analyze is your friend
perhaps there's a path available which would work for this read of it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast)---
TIP 7: You can help support
= construct_array(elems, n, INT4OID, 4, true, 'i');
PG_RETURN_ARRAYTYPE_P(retval);
}
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast)---
TIP 7: You can help
Gregory Stark [EMAIL PROTECTED] writes:
Aside from some autoconf tests and the documentation for the GUC I
think it's all in there.
I'm sorry, it seems I accidentally grabbed an old tree to generate this patch.
I'll send along a better more recent version. Argh.
--
Gregory Stark
()*100)::integer from generate_series(1,100)));
bitmap-preread-v8.diff.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---(end of broadcast
.
Not sure how easy it would be to shoehorn into t he like processing, I could
look at that if you want.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadcast
the opposite problem. The patch was fairly heavily tested on this end before
it was posted and I'm not sure those tests have been repeated since the merge.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support
the outermost session user's ID instead of current
ID, but that might only move the security risks someplace else.
Thoughts?
Perhaps we should only do this if the current user's ID is the same as the
outermost session user's ID?
--
Gregory Stark
EnterpriseDB http
Gregory Stark [EMAIL PROTECTED] writes:
There's no way the other transaction's timeout could fire while we're doing
this is there? Are we still holding the lw locks at this point which would
prevent that?
Ah, reading the patch I see comments indicating that yes that's possible and
no, we
of the passbyval nature of int8, the !AggState version is not slower
than using the pointer directly.
Does this mean count() and sum() are slower on a 32-bit machine?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about
.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
Zoltan Boszormenyi írta:
Gregory Stark írta:
4) Your problems with tsearch and timestamp etc raise an interesting
problem.
We don't need to mark this in pg_control because it's a purely a run-time
issue and doesn't affect on-disk storage
as we add more and more system functions too.
It might be cute to see if the pattern matches any user functions and if not
try again with system functions. So you would still get results if you did
\df rtrim for example.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
It might be cute to see if the pattern matches any user functions and if not
try again with system functions. So you would still get results if you did
\df rtrim for example.
Interesting idea. IIUC, \df would give
Tom Lane [EMAIL PROTECTED] writes:
Gregory Stark [EMAIL PROTECTED] writes:
One --perhaps nice, perhaps not-- property of this is that if you defined a
function named rtrim and then did \df rtrim it would show you _both_ the
system and user function and make it easier to see the conflict
of non-globbing cases for pattern. As in, I
would want \df rtrim to work. I suppose it could be annoying to have to type
\df public.* -- there's nothing stopping us from having \dfU and \dfS too I
suppose, though I doubt most people would find them.
--
Gregory Stark
EnterpriseDB http
101 - 200 of 237 matches
Mail list logo
