to people inspecting pg_depend, for example; but
then, it's foolish not to be using regclass in that case.
Whether a table is bootstrap or not doesn't seem useful to me.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc
Bernd Helmle wrote:
--On Donnerstag, August 24, 2006 22:25:46 +0200 Bernd Helmle
[EMAIL PROTECTED] wrote:
--On Montag, August 21, 2006 02:07:41 -0400 Alvaro Herrera
[EMAIL PROTECTED] wrote:
If someone wants to look at the current updatable view patch, please look
at this current
are debating it again.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
more by observing brace position in
if/else ;-)
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Zoltan Boszormenyi wrote:
Andrew Dunstan írta:
Alvaro Herrera wrote:
Böszörményi Zoltán wrote:
what's the problem with COPY view TO, other than you don't like it? :-)
The problem is that it required a ugly piece of code. Not supporting it
means we can keep the code nice. The previous
), is it enough for you? Or would you insist on
also having
copy view to stdout;
?
We can, and the posted patch does, support the first form, but not the
second. In fact I deliberately removed support for the second form for
Zoltán's patch because it uglifies the surrounding code.
--
Alvaro Herrera
Zoltan Boszormenyi wrote:
Alvaro Herrera írta:
Remember that we were talking about supporting views, not tables. And
if a view uses a slow query then you are in immediate danger of having a
slow COPY. This may not be a problem but it needs to be discussed and
an agreement must be reached
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
My question is, if we allow this:
copy (select * from view) to stdout;
(or to a file, whatever), is it enough for you? Or would you insist on
also having
copy view to stdout;
?
We can, and the posted patch does, support
* from view). The latter we can have without
discussion -- from me, that is :-)
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast
Zoltan Boszormenyi wrote:
Alvaro Herrera írta:
But COPY view (col1, col2, ...) TO may still be
useful even if the COPY (SELECT ...) (col1, col2, ...) TO
is pointless. [1]
Hum, I don't understand what you're saying here -- are you saying that
you can't do something with the first form
Zoltan Boszormenyi wrote:
Alvaro Herrera írta:
Zoltan Boszormenyi wrote:
Alvaro Herrera írta:
But COPY view (col1, col2, ...) TO may still be
useful even if the COPY (SELECT ...) (col1, col2, ...) TO
is pointless. [1]
Hum, I don't understand what you're saying here
are also committers. Some Major
Developers are committers as well).
There is no committee. The closer you get to that, is people vocal
enough on pgsql-hackers.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc
Zoltan Boszormenyi wrote:
Alvaro Herrera írta:
Zoltan Boszormenyi wrote:
I think at this point is someone else's judgement whether you can put it
back or not. Tom already said that he doesn't object to the feature per
se; no one else seems opposed to the feature per se, in fact.
Now
Hi,
I just detected another problem with building ecpg in a VPATH
environment. This patch fixes it for me.
This is needed because ecpg_config.h ends up in the build dir rather
than the source dir.
Thanks,
--
Alvaro Herrerahttp://www.CommandPrompt.com
copyselect regression test is not added to
the serial schedule.
I'll repost a reworked version at some point, if no one beats me to it.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Index: doc/src/sgml/ref/copy.sgml
Böszörményi Zoltán wrote:
So when will you send in a revised patch?
Soon. :-)
No, don't send it soon. We're in feature freeze already (and have
been for three weeks). You need to send it now.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL
to reject it.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
case for the
SELECT.
That doesn't help you with the UNION stuff though.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP
that patches are posted and no action is taken on them for
months. I agree with that.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast
Bernd Helmle wrote:
I'll try to complete the missing comments and to make some statements
cleaner.
Thanks.
--On Montag, August 21, 2006 02:07:41 -0400 Alvaro Herrera
[EMAIL PROTECTED] wrote:
The new files are src/backend/rewrite/viewUpdate.c and
src/include/rewrite/viewUpdate.h
remove
the piece of code from the viewUpdate.c file, your sample script works.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 3: Have you
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Ok, this patch implements more or less this idea; except that instead of
checking the list of implicit dependencies for later objects, we iterate
twice on the list of objects to delete, and create a list of implicit
dependencies
int);
create table tt2 (f1 int primary key);
alter table tt1 add foreign key (f1) references tt2;
grant references on table tt2 to bar;
\c - bar
alter table tt3 add foreign key (f1) references tt2;
\c - foo
drop owned by foo;
drop owned by foo cascade;
--
Alvaro Herrera
.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
it.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
since that much complexity isn't justified
IMHO.
Hum, but two columns here seem warranted, don't they?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast
behavior on non-broken
platforms. Or maybe there's a better solution.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 2
. This is okay
to
! * change as int64 as we do it on every fetch. (The Executor must not
* assume that dest never changes.)
*/
if (queryDesc)
Too enthusiastic about the search'n replace I think.
I stopped reading at this point.
--
Alvaro Herrera
script -- ISTM you should put the
DROP commands there, not in the install script.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 1: if posting
with
pgindent.
Regarding the pg_relpages function, why do you think it's necessary?
(It returns the true number of blocks of a given relation). It may
belong into core given a reasonable use case, but otherwise it doesn't
seem to belong into pgstatindex (or pgstattuple for that matter).
--
Alvaro
This patch allows ECPG to build on a VPATH build. I didn't commit it
just because I don't have a non-VPATH build to make sure it still works ...
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Index: test
LENGTH STRUCTURE */
Which might give you an idea ...
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
/these/ ?
Otherwise looks good to my untrained eyes.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
links. Maybe we should consider adding
this as a section in the external projects chapter, instead of having a
chapter of its own, but some links seems a little short on actual
contents.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
I don't think this sort of material belongs directly into the PostgreSQL
documentation.
Why not?
Well Peter said that, not me :)
I know, but I though I'd post one message instead of two. (In fact I
didn't even think
Tom Lane wrote:
Joe Conway [EMAIL PROTECTED] writes:
The good news is that from a memory and perfomance standpoint, my simple
test now shows us outperforming mysql:
Sweet ;-)
I love this team. Kudos!
--
Alvaro Herrerahttp://www.CommandPrompt.com
Hannu Krosing wrote:
Ühel kenal päeval, P, 2006-07-30 kell 14:11, kirjutas Alvaro Herrera:
What was idea behind moving vac_update_relstats to a separate
transaction? I'm wondering if it's still needed, if it further enhances
the system somehow, or your patch did something differently than
Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Ãhel kenal päeval, P, 2006-07-30 kell 14:11, kirjutas Alvaro Herrera:
What was idea behind moving vac_update_relstats to a separate
transaction? I'm wondering if it's still needed, if it further enhances
the system somehow
-- sorry I typo'ed your name in the commit message though :-(
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 1
Bruce Momjian wrote:
I thought these new functions were going to be merged into
/contrib/pgstattuple.
Well, that's exactly what this patch seems to do ...
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc
. But at this point I wouldn't hold my breath
on that
The alternative seems to be that the Slony-I team doesn't feel they have
a need for it, nobody else pushes hard enough for the feature to be in
core, and thus Slony-I and all the rest stays broken forever.
--
Alvaro Herrerahttp
)
+ {
+ val *= KILOBYTE;
+ used = true;
+ endptr += 2;
+ }
Does this mean that one must match the kB exactly, with the specified
upper and lower case?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL
doing?
You mean having VACUUM VERBOSE return a result set?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 1: if posting
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Hannu Krossing asked me about his patch to ignore transactions running
VACUUM LAZY in other vacuum transactions. I attach a version of the
patch updated to the current sources.
nonInVacuumXmin seems useless ... perhaps a vestige
Cc: pgsql-hackers removed, as this mail contains a patch.
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Hannu Krossing asked me about his patch to ignore transactions running
VACUUM LAZY in other vacuum transactions. I attach a version of the
patch updated to the current
Satoshi Nagayasu wrote:
Hi,
I'm working on an utility for b-tree index, called `pgstatindex`.
Does it make sense to merge the pgstatindex stuff with pgstattuple, and
have the fragmentation report into pgstatindex instead of pgstattuple
itself?
--
Alvaro Herrera
also noticed the Makefile does not handle VPATH, but
I didn't fix it. Patches welcome.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 5: don't
truncation point is calculated
differently and thus we don't need to take special care about this.
--
Alvaro Herrerahttp://www.advogato.org/person/alvherre
Uno combate cuando es necesario... ¡no cuando está de humor!
El humor es para el ganado, o para hacer el amor, o
-wide vacuums for non-connectable databases (template0), and
normal per-table vacuuming for database that are in actual use.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
What I'm after is not freezing for read-only media, nor archive, nor
read-only tables. What I'm after is removing the requirement that all
databases must be vacuumed wholly every 2 billion transactions
Hum, how are you handling the case where I specify
CREATE TABLE LIKE x INCLUDING CONSTRAINTS EXCLUDING CONSTRAINTS ?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast
Alvaro Herrera wrote:
Here I repost the patch to implement non-transactional catalogs, the
first of which is pg_ntclass, intended to hold the non-transactional
info about pg_class (reltuples, relpages).
I forgot to attach the new file pg_ntclass.h (src/include/catalog).
Here
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Would it work to do
#define tid ItemPointerData
...
tid relntrans;
...
#undef tid
?
Yeah, it probably would. I'll try.
The *real* problem with what you've done is that pg_class.h now depends
on having
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
This is the relminxid patch corresponding to the pg_ntclass patch I just
posted.
That disable_heap_unfreeze thing seriously sucks. How bad are the API
changes needed to pass that as a parameter instead of having a
very-dangerous
);
Datum pg_file_unlink(PG_FUNCTION_ARGS);
Datum pg_logdir_ls(PG_FUNCTION_ARGS);
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 4: Have you
to implement a patch, include them separately,
indicating in the patch description in which directory they are meant to
reside.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end
)));
break;
This should depend on the GUC variable for the patch to work at all ...
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
CREATE TABLE foo (a int);
for some unknown reason, an inval message involving relation foo seems
to be emitted.
heap_unfreeze(pg_class)
CommandCounterIncrement()
heap_unfreeze(pg_attribute)
CommandCounterIncrement
that should not be.
I'm wondering if we need a second pg_class-derived catalog that carries
just the nontransactional columns.
I hope we don't need to do this because ISTM it will be a very big change.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Well, if a transaction modifies a table in some way, even without
changing the data, should generate an unfreeze event, because it will
need to lock the table; for example AlterTable locks the affected
relation
, and apparently tab
expansion as well.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 5: don't forget to increase your free
to change the semantics of the
ArchPid variable in postmaster. We use those to keep track of the
running process, so if there's no archiver, it should be 0 (which is
true for all said variables).
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication
rewrite this piece of code.
Ah, there's another reason, and it's that I'm rewriting the tuple in
place, not calling heap_update. I'm not sure if I can reuse
log_heap_update for this purpose -- I'll take a look.
--
Alvaro Herrerahttp://www.CommandPrompt.com
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Ah, there's another reason, and it's that I'm rewriting the tuple in
place, not calling heap_update.
Is that really a good idea, as compared to using heap_update?
Not sure -- we would leave dead tuples after the VACUUM is finished
.
If you don't, I'll eventually come back to it, but I'm not sure when
will that be.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 5: don't forget
for applying the
patch as-is, no strict mode necessary (because, as you say, it's easy
to get it wrong).
Can the Debian build script be fixed? Does the RPM spec have the same
problem?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt
in pg_shdepend for a RELKIND_COMPOSITE_TYPE relation (i.e. the first
solution proposed above). I intend to apply it to 8.1 and current
trunk, later today.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Index
Alvaro Herrera wrote:
Tom Lane wrote:
I'd argue that you should do nothing, ie, dropping a table should never
affect datminxid. The proper interpretation of the pg_database columns
is that we guarantee that all XID's in the database are *at least* thus-
and-so, not that the minimum
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
BTW, I forgot to mention that I intend to apply this patch later today,
regardless of whatever solution we may decide for the problem below; we
can add it later, and it certainly is a corner case.
Please don't. If you don't have
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
3. automatically change the first single-table VACUUM in a database into
a database-wide vacuum. Additionally to the problems from the precedent
proposal, this one breaks principle of least surprise.
This isn't as bad as all
the
statistics file very often, compared to how frequent it's written today.
If somebody tries to read something from the pgstat file, is the backend
going to request a rewrite and wait until it is complete?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I just noticed a problem, which is why I labeled it a WIP: the current
implementation turns pg_database.datminxid to InvalidTransactionId when
the table that has the minimum relminxid is dropped.
I'd argue that you should do
(you could say bogus) when the query buffer is
longer than the terminal. Not sure if that's a problem of the patch or
it has always been like this. It's possible to workaround using \e.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication
...]
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
I intend to apply it tomorrow.
--
Alvaro Herrerahttp://www.PlanetPostgreSQL.org
One man's impedance mismatch is another man's layer
Neil Conway wrote:
On Sun, 2006-03-19 at 23:11 -0400, Alvaro Herrera wrote:
Here's a little cosmetic patch merging the loading of regular
descriptions with shared descriptions (just like the process of loading
regular dependencies was merged with shared dependencies).
Where's the patch
the line/character position should be
returned in a separate error attribute in ereport. So for example
pgAdmin could count characters and mark it in bold or use a different
color.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc
(thousands?) of synonyms.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast)---
TIP 6: explain analyze is your friend
changes are important. For example when you
indent a piece of code one level higher. The submitter should eyeball
the patch (in diff form) and clean things up when something unexpected
appears, like a no-op whitespace change.
--
Alvaro Herrerahttp
Bruce Momjian wrote:
I have remove the LEFT part of the join to pg_roles in
psql/description.c. I assume this is too risky for 8.1.X.
Well, 8.1 already has per-role dependencies, so why not do it?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL
*found_earlier)
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
, as patches have been floating since before 8.0 and
we still don't have it.
--
Alvaro Herrera Developer, http://www.PostgreSQL.org
Si quieres ser creativo, aprende el arte de perder el tiempo
---(end of broadcast)---
TIP 6: explain
that, context information.
--
Alvaro Herrerahttp://www.advogato.org/person/alvherre
World domination is proceeding according to plan(Andrew Morton)
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Mark Kirkwood wrote:
Yes it would - I usually build the SGML - HTML, then cut the code out
of a browser session to test - the pain is waiting for the docs to build.
FWIW, what I do is to build a cut-down version of postgres.sgml to
include only the file you want to check. I think there is a
, tentative_source = PGC_S_DEFAULT,
source = PGC_S_DEFAULT, stack = 0x0},
variable = 0x100136d2, reset_val = 2, min = 1.5, max = 2, assign_hook = 0,
show_hook = 0, tentative_val = 0}
--
Alvaro Herrera http://www.amazon.com/gp/registry/CTMLCN8V17R4
La grandeza es una experiencia
table's operations? Also why force it to activate the abort-on-error
mode?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
---(end of broadcast)---
TIP 2: Don't 'kill -9
Qingqing Zhou wrote:
Add a note to Win32 gettimeofday() emulation.
Applied, thanks.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast
Simon Riggs wrote:
On Fri, 2005-12-16 at 16:04 -0300, Alvaro Herrera wrote:
Simon Riggs wrote:
The following patches add a -N option to psql and pgrestore.
This option adds a BEGIN at the start and a COMMIT at the end of all
commands, causing all statements to be executed
don't think you can actually get the desired
results --- certainly it would be a nontrivial amount of work to get
any useful behavior like that.
Ah, quite true. I withdraw my comments then.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication
of the whole thing? We could show additional
columns in the pg_prepared_statements, indicating whether this is
PREPARE (and the statement's name) or a Parse message.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc
database systems is not directly applicable to Postgres.
Keep in mind that in Postgres we don't have host variables, which is
what is needed to make OUT params work the way you are assuming they do.
This could be improved in the future but currently that's the way it is.
--
Alvaro Herrera
, and
then you can commit there. This someone is probably Peter, though I
could do it if he's not available.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---(end of broadcast
--
12674
(1 fila)
alvherre=# select factorial_length(6000);
factorial_length
--
20066
(1 fila)
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
So this is a psql bug?
Not here. Do you see it?
Actually, no. If I cut'n paste the number from psql to
cat foo
shift insert
then only 4096 chars are copied. (Amusingly, I can't add a newline to
^D and close the file. I must
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Actually, no. If I cut'n paste the number from psql to
cat foo
shift insert
then only 4096 chars are copied. (Amusingly, I can't add a newline to
^D and close the file. I must delete one char to do that.)
Hmm, cut buffer
Alvaro Herrera wrote:
I intend to apply later today the attached patch in order to reduce some
code duplication in aclchk.c and clean a bit the API I just introduced
in the previous patch. This reduces aclchk.c from 2377 lines to 2206.
I applied this patch yesterday, but I did not receive
/projects/public/pgsql/browser/trunk/pgsql
It has the additional advantage over our current CVSweb that it's set
with tabs to 4 spaces, so it looks just like our code is supposed to ...
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting
Martijn van Oosterhout wrote:
On Sun, Nov 27, 2005 at 06:30:59PM -0300, Alvaro Herrera wrote:
Martijn van Oosterhout wrote:
Attached is a patch which applies this filtering to the backend and has
the same results as linking with --as-needed. I basically took the
filter list of libpq
Peter Eisentraut wrote:
Alvaro Herrera wrote:
This patch allows pg_regress to be installed by default. This was
proposed awhile back but never done, any objections if I commit this?
If you do, there should also be documentation, such as a reference page,
about how to use it.
Applied
Peter Eisentraut wrote:
Alvaro Herrera wrote:
This patch allows pg_regress to be installed by default. This was
proposed awhile back but never done, any objections if I commit this?
If you do, there should also be documentation, such as a reference page,
about how to use it.
Ok
-ldl? How do we implement OPEN etc if not without
dlopen()? [looks around] I see this is with pg_dlopen which in turn is
dlopen in Linux and others. Did you try contrib's regression test?
plperl's?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL
401 - 500 of 726 matches
Mail list logo
