rstand the general rules where it may be much
harder to try avoidance)
Cheers, John
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
While I do not know QGIS, I'm wondering if it's similar to some of our
applications where they always use the same system login for the database
while each user provides a unique login to the application. Have you ever
set log_connections in your postgresql.conf file? That would show you which
user
will be faster due to not having to examine
more than one hash bucket array most of the time.
--
John Gorman
http://www.enterprisedb.com
dht-v2-resize-cleanup.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Do a web search on setting shared memory the hard way, and I think you'll see
what you really need to do.
--
Jay
Sent from my iPad
> On Nov 10, 2016, at 5:57 PM, leoaaryan wrote:
>
> I am a newbie to databases and Postgres and I am trying to analyze the shared
> memory being calculated and all
On Tue, Oct 4, 2016 at 10:11 PM, Tomas Vondra
For GenSlab the situation is less clear, as there probably are ways to make
> it work, but I'd vote to keep it simple for now, and simply do elog(ERROR)
> in the realloc() methods - both for Slab and GenSlab. The current use case
> (reorderbuffer) does
set->aset, size);
On Sat, Oct 1, 2016 at 10:15 PM, Tomas Vondra
wrote:
> On 10/02/2016 12:23 AM, John Gorman wrote:
>
>> I reproduced the quadradic pfree performance problem and verified that
>> these patches solved it.
>>
>> The slab.c data structures and function
ments could be clearer.
Perhaps this is what is meant.
< * (plus alignment), now wasting memory.
> * (plus alignment), not wasting memory.
In slab.c some lines are over 80 characters could be folded.
It would be nice to give each patch version a unique file name.
Nice patch, I enjoyed readi
On Mon, Aug 1, 2016 at 9:39 PM, Michael Paquier
wrote:
> On Tue, Aug 2, 2016 at 2:08 AM, Robert Haas wrote:
> > Did you add this to the next CommitFest?
>
> I have added it here:
> https://commitfest.postgresql.org/10/691/
> John, it would be good if you could get a comm
On Tue, Jul 26, 2016 at 9:44 PM, Michael Paquier
wrote:
> On Wed, Jul 27, 2016 at 12:41 AM, John Harvey
> wrote:
> > Because of this, I've submitted a small patch which fixes the verbosity
> of
> > the error message to actually explain what's missing. I h
g just to figure out what the problem is.
Because of this, I've submitted a small patch which fixes the verbosity of
the error message to actually explain what's missing. I hope that this
patch will be considered for the community, and it would be nice if it was
back-patched.
Attached
operations with a spinlock?
Thanks!
John
Hi everyone!
Trying to make VACUUM FREEZE on PG instance and keep getting this error:
2016-03-18 05:56:51 UTC 46750 WARNING: oldest xmin is far in the past
2016-03-18 05:56:51 UTC 46750 HINT: Close open transactions soon to
avoid wraparound problems.
2016-03-18 05:56:51 UTC 46750 DEBUG:
is weird.
How can I calculate how long DB can live in this stage?
2016-03-19 0:28 GMT+03:00 Tomas Vondra :
> Hi,
>
> On 03/18/2016 09:42 AM, John Snow wrote:
>
>> Hi everyone!
>>
>> Trying to make VACUUM FREEZE on PG instance and keep getting this error:
>>
On Sat, Feb 27, 2016 at 9:25 AM, Robert Haas wrote:
> On Sat, Feb 27, 2016 at 7:08 PM, Andrew Dunstan
> wrote:
>
> > Perhaps what we need to do is modify pg_regress.c slightly to allow more
> > than one --temp-config argument. But that could be done later.
>
> Well, I'm pretty interested in usin
to preserve any available error state.
I am attaching a patch to preserve errno across errmsg() calls.
Does this seem like a good idea?
Best, John
errmsg-errno-v1.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On OSX:
SELECT asin(2);
> asin
> --
> NaN
> (1 row)
>
SELECT asin(2);
> asin
> --
> NaN
> (1 row)
The attached patch brings OSX into line with the expected behaviour and the
additional regression tests verify this.
Is this worth fixing and if so what is
I have confirmed that "-Wno-unused-command-line-argument"
suppresses the "-pthread" warning for clang 6.0 and does not
trigger a warning in gcc 4.9.
Works for me!
John
On Fri, Apr 3, 2015 at 5:21 PM, Tom Lane wrote:
> I wrote:
> > Peter Eisentraut writes:
> &g
lib/
./src/interfaces/ecpg/ecpglib/
./src/interfaces/ecpg/compatlib/
./src/interfaces/ecpg/preproc/
This is interfering with using "-Wall -Werror" to catch warnings.
Any opinions as to whether this is worth fixing and if so
what the cleanest approach might be?
Thanks, John
On Tue, Jan 13, 2015 at 7:25 AM, John Gorman wrote:
>
>
> On Sun, Jan 11, 2015 at 6:00 PM, Robert Haas
> wrote:
>
>> On Sun, Jan 11, 2015 at 6:01 AM, Stephen Frost
>> wrote:
>> > So, for my 2c, I've long expected us to parallelize at the relation-file
On Sun, Jan 11, 2015 at 6:00 PM, Robert Haas wrote:
> On Sun, Jan 11, 2015 at 6:01 AM, Stephen Frost wrote:
> > So, for my 2c, I've long expected us to parallelize at the relation-file
> > level for these kinds of operations. This goes back to my other
> > thoughts on how we should be thinking
This patch implements the first wiki/Todo Configuration Files item
"Consider normalizing fractions in postgresql.conf, perhaps using '%'".
The "Fractions in GUC variables" discussion is here.
http://www.postgresql.org/message-id/467132cf.9020...@enterprisedb.com
This patch implements expressing
field as opposed to the beginning of the field? That would allow
pglz to see what it wants to see early on and go to work when possible?
Add an offset at the top of the field to show where to look - but then it
would be the same in terms of functionality outside of that? Or pretty
close?
John
On Thu, Aug 7, 2014 at 11:07 AM, Robert Haas wrote:
> On Tue, Aug 5, 2014 at 8:15 PM, Peter Geoghegan wrote:
> > "The adversarial method works for almost any polymorphic program
> > recognizable as quicksort. The subject quicksort may copy values at
> > will, or work with lists rather than array
I just browsed the paper linked by Peter and it looks like the attack has
to be active against a currently executing qsort. In the paper, what
happens is the comparison function is supplied by the attacker and
effectively lies about the result of a comparison. It keeps the lies
consistent in a very
Greetings,
I took at look at the TODO list and got interested in the possible
optimization of the bcTruelen() function. Read the archived messages about
that subject and decided to see what could be done.
I tested the performance of 5 different versions of bcTruelen().
1. The code as it exists in
On Sat, Jul 19, 2014 at 11:58 AM, Michael Banck wrote:
SNIP
>
> Maybe if you pgindent the IANA code as well, you can more easily diff
> the actual changes between the two, did you try that?
>
>
> Michael
>
Unfortunately, pgindent doesn't work well with the IANA code as evident by
some previous ch
that pgindent not be
used again on the IANA code so future maintainers can easily perform a diff
between the IANA code and the postgres code to determine the actual
differences. I'll then see about doing the same with the other source files
in timezone.
On Fri, Jul 18, 2014 at 4:27 PM, Tom Lan
On Fri, Jul 18, 2014 at 1:21 PM, Tom Lane wrote:
> John Cochran writes:
> > My proposal is the have the following directory structure
>
> ...
> > 1. I would have liked to recommend 2 sub-directories underneath
>
...
>
>
I have exactly zero expectation of using
unk" files
into the directory. The files would mainly consist of man pages and html
files containing documentation for the timezone code. The extra files would
consume approximately 500 kilobytes above what's actually needed, but
otherwise wouldn't have any adverse effects.
Thank you
assignment of an int to a
long?" Or to put it another way, "Are there any C compilers that fail to
properly perform integer promotion from int to long?"
As things stand, it looks to me like that function eitol() can be simply
deleted and the 22 calls to that function also removed. Shorter,
simpler,faster code is always a good thing after all.
Thank you for reading,
John Cochran
e every week or so (every day would
really eat into cycles for other packages).
John
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
My cut'n'pasting failed me at one point corrected below.
> discussion about what is the difference between a synchronous read
> versus an asynchronous read as far as non-originator waiting on it is
> concerned.
>
> I thought a bit more about this. There are currently two differences,
> one of
res=# CREATE SCHEMA testschema;
CREATE SCHEMA
postgres=# CREATE TABLE testschema.testtable (testserial serial PRIMARY
KEY, testchar varchar (100) NOT NULL);
CREATE TABLE
I don't know enough to really test this. Can you recommend a simple script
to do some PostgreSQL testing?
John
--
L can run on a VAX with only 20 MB or so of
resident memory.
Thanks,
John
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
y
'/usr/pkgsrc/databases/postgresql93-server/work/postgresql-9.3.4/src/port'
../../../src/Makefile.global:423: recipe for target 'submake-libpgport'
failed
gmake: *** [submake-libpgport] Error 2
That's all I have time for tonight. Is there an easier way to ru
However,
considering how much memory it uses, I wonder how many people would
actually use it. I did run Apache / MySQL / PHP on a VAXstation 4000/60
not long ago, but MySQL takes way too much memory, too. Don't even get me
started on how memory PHP uses - someone has to write some good
Asynchronous IO - proposal and patch
>
> On 06/24/2014 04:29 PM, John Lumby wrote:
>>> On Mon, Jun 23, 2014 at 2:43 PM, John Lumby wrote:
>>>> It is when some *other* backend gets there first with the ReadBuffer that
>>>> things are a bit trickier. The current version
ers@postgresql.org
>
> On Mon, Jun 23, 2014 at 2:43 PM, John Lumby wrote:
>> It is when some *other* backend gets there first with the ReadBuffer that
>> things are a bit trickier. The current version of the patch did polling for
>> that case
>> but that drew critic
> Date: Thu, 19 Jun 2014 15:43:44 -0300
> Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch
> From: klaussfre...@gmail.com
> To: st...@mit.edu
> CC: hlinnakan...@vmware.com; johnlu...@hotmail.com;
> pgsql-hackers@postgresql.org
-originator of an aio_read to wait on completion
(LWlock instead of polling the aiocb)
This was talked about in several earlier posts and Claudio is also
working on something there
. package up my benchmark
Cheers John
> Date:
> Date: Thu, 29 May 2014 18:00:28 -0300
> Subject: Re: [HACKERS] Extended Prefetching using Asynchronous IO - proposal
> and patch
> From: klaussfre...@gmail.com
> To: hlinnakan...@vmware.com
> CC: johnlu...@hotmail.com; pgsql-hackers@postgresql.org
>
> >>>
> >>> Even if it worked on Linux tod
> From: t...@sss.pgh.pa.us
> To: klaussfre...@gmail.com
> CC: hlinnakan...@vmware.com; johnlu...@hotmail.com;
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Extended Prefetching using Asynchronous IO - proposal
> and patch
> Date: Thu, 29 May 2014 17:56:57 -0400
>
> Claudio Freire wr
2014 at 5:39 PM, Heikki Linnakangas
> wrote:
> > On 05/29/2014 11:34 PM, Claudio Freire wrote:
> >>
> >> On Thu, May 29, 2014 at 5:23 PM, Heikki Linnakangas
> >> wrote:
> >>>
> >>> On 05/29/2014 04:12 PM, John Lumby wrote:
> >>&
sounds as though Claudio is on it too).
The area of exactly what the best prefetch strategy should be for
each particular type of scan and context is a good one to work on.
John
> Date: Wed, 28 May 2014 18:12:23 -0700
> Subject: Re: [HACKERS] Extended Prefetching using Asynchronous IO - pr
>
> On 05/28/2014 11:52 PM, John Lumby wrote:
> >
>
> The patch seems to assume that you can put the aiocb struct in shared
> memory, initiate an asynchronous I/O request from one process, and wait
> for its completion from another process. I'm pretty surprised if th
On Mon, Apr 14, 2014 at 2:06 PM, Stefan Kaltenbrunner <
ste...@kaltenbrunner.cc> wrote:
> On 04/13/2014 10:19 PM, John Mudd wrote:
> >
> > On Sun, Apr 13, 2014 at 12:04 PM, Euler Taveira > <mailto:eu...@timbira.com.br>> wrote:
> >
> > On 13-04-2
], 1, 3000) = 0
close(3)= 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
writev(1, [{"/tmp:5432 - no response", 23}, {"\n", 1}], 2) = 24
exit_group(2) = ?
For my next step I'll try building musl Postgres with the --enable-cassert
option. What else can I do to debug this?
John
I'm writing a pgsql extension in C, which is multithreaded. The SPI
connection is global, so do I have to implement a lock to make sql queries
in each thread, or can I make a connection on a per-thread basis?
"some Salesforce folks" that would be me! It looks like I didn't quite
communicate to Tom just what I was looking for as I do indeed want to have
a variable number of "any" types, as:
CREATE AGGREGATE FOO ( ANYELEMENT, , VARIADIC "any") (
...
STYPE = ANYARRAY
...)
so the corresponding transi
I see a few old messages referring to ISAM to SQL emulation.
For example:
http://www.postgresql.org/message-id/200402171616.i1hgg9u11...@candle.pha.pa.us
Does anyone know of any actual source code to one of these projects? Any
active projects?
John
sm in your disk hardware, file system, etc.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 1/23/2013 8:32 PM, Tom Lane wrote:
FWIW, in Fedora-land I see:
F16: 2.1.6 (F16 will go out of support next month)
F17: 2.1.10 (F17 has been stable for 6+ months)
F18: 2.1.12 (F18 just went stable)
While requiring 2.1.10 today might be thought a tad leading-edge,
will that still
On 1/20/2013 9:23 PM, Vivek Singh Raghuwanshi wrote:
3.RedHat_RHEL-6
uuid-devel (Now RedHat is not providing this rpm)
you sure about that? now, I'm running CentOS 6 not RHEL6, but the
packages are 1:1 and built from the same SRPMs.
uuid-devel.i686
1.6.1-10.el6
On 1/11/2013 6:56 AM, Steve Singer wrote:
If someone else in the community is running PostgreSQL on AIX then it
would be good if they setup a buildfarm member, perhaps with a more
recent version of AIX.
I am and I'd love to, however, sigh, its deep behind corporate firewalls
and any attempt
On 1/7/2013 2:05 AM, Andres Freund wrote:
I think there should be enough bits available in the toast pointer to
indicate the type of compression. I seem to remember somebody even
posting a patch to that effect?
I agree that it's probably too late in the 9.3 cycle to start with this.
so an upgra
On 1/7/2013 1:10 AM, Simon Riggs wrote:
On 7 January 2013 07:29, Takeshi Yamamuro
wrote:
>Anyway, the compression speed in lz4 is very fast, so in my
>opinion, there is a room to improve the current implementation
>in pg_lzcompress.
So why don't we use LZ4?
what will changing compression
On 12/20/2012 4:17 AM, Brett Maton wrote:
It appears that procpid has been renamed to pid at some point, also
the column current_query appears to have been shortened to query.
My patch updates a couple of queries to use the new shorter column names.
IMHO, any such fix should check the ver
On 12/20/2012 12:26 AM, Gavin Flower wrote:
CREATE TABLE test (id int, int sub, text payload);
CREATE INDEX test_idx1 ON test (id, sub);
CREATE INDEX test_idx2 ON test (id);
Nowtest_idx2 is logically included intest_idx1, but if the majority of
transactions only query onid, thentest_idx2 wou
On 12/5/2012 1:42 AM, Simon Riggs wrote:
I think we need a parameter called
schema_change_reporting = off (default) | on [USERSET]
which displays relevant statistics/reports about the actions taken by
DDL statements. That will also highlight locks and the need to reduce
their lock levels.
w
On 11/27/12 2:41 PM, Tom Lane wrote:
Tweaking the casting rules could have a lot of
unforeseen consequences.
understatement of the year. IMHO. $0.02 worth etc.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql
Bruce Momjian wrote:
>
> On Fri, Nov 2, 2012 at 09:59:08AM -0400, John Lumby wrote:
> > However,the OP describes an implementation based on libaio.
> > Today what we have (for linux) is librt, which is quite different.
>
> Well, good thing we didn't switch to
zed chunks for this?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 11/04/12 11:59 AM, Jeff Davis wrote:
Is there any fundamental or philosophical reason why a foreign table
can't accept arguments? Should that be a TODO?
what does that even mean?how would 'data' accept 'arguments' ??!
--
john r pierce
t thread.
4. Each waiting backend receives the completion
and the last one does the housekeeping and returns the pg_buf_aiocb.
What complicates it is managing the associated pinned buffer
in such a way that every backend takes the correct action
with the correct degree of serialization of the buffer descriptor
during critical sections, but yet allowing all backends in
3. above to concurrently wait/check. After quite a lot of testing
I think I now this correct. ("I just found the *last* bug!" :-)
John
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
If I recall, the
glic (librt) aio does have an lio_listio but it is either a noop
or just loops over the list, I forget which (don't have its source right now),
but in any case I am sure there is a potential for implementing such a facility.
But to be r
rface to
PrefetchBuffer
and add a new DiscardBuffer which I did not include in this snapshot to avoid
confusing.
John
--- src/backend/executor/nodeIndexscan.c.orig 2012-10-31 15:24:12.083163547 -0400
+++ src/backend/executor/nodeIndexscan.c 2012-11-
ve a proper setup this week but will reply at greater length
next week.
John
just finished processing) and this
makes them much easier to follow. Statement level TRIGGERs can be used
for audit logs and similar operations which need to run once per
statement.
as a relative novice, I concur, this is clear, concise, and to the point.
--
john r pierceN
:)
Any such comparison should be with something that is common knowledge,
not something even more obscure than the primary subject matter.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers ma
d libpq.so certainly has
libssl3.so, etc as references. ditto the postmaster/postgres main
program has libssl3.so too. maybe your certificate chains don't come
pre-built, I dunno, I haven't dealt with that end of things.
--
john r pierceN 37,
's other than Linux to consider too... the
various BSD's, Solaris, AIX, OSX, and MS Windows are all platforms
PostgreSQL runs on.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (p
t think we have that.
me thinks this would be extremely useful for importing 'dirty' data.
that or a per-connection flag (or option on the COPY command?) that
said "substitute-on-error" for the likes of UTF-8 imports from CSV.
--
john r pierce
it to the database encoding and generate an error on any invalid
character. this translation could be identity (eg, UTF8->UTF8)
whereupon it would just validate.a 2nd function would do the same,
but replace errors with the substitution character in the target charset
and not error.
--
On Mon, Oct 1, 2012 at 11:58 AM, Dan Scott wrote:
> Hi John:
>
> On Sun, Sep 30, 2012 at 11:45 PM, john knightley
> wrote:
>> Dear Dan,
>>
>> thank you for your reply.
>>
>> The OS I am using is Ubuntu 12.04, with PostgreSQL 9.1.5 installed on
>> a
On Mon, Oct 1, 2012 at 12:11 PM, Tom Lane wrote:
> john knightley writes:
>> The OS I am using is Ubuntu 12.04, with PostgreSQL 9.1.5 installed on
>> a utf8 local
>
>> A short 5 line dictionary file is sufficient to test:-
>
>> raeuz
>> 我们
>> 𦘭𥎵
&g
loaded from
http://gdzhdb.l10n-support.com/sawndip-fonts/Sawndip.ttf)
The last two words even though included in a dictionary do not get
accepted by ts_vector.
Regards
John
On Mon, Oct 1, 2012 at 11:04 AM, Dan Scott wrote:
> On Sun, Sep 30, 2012 at 1:56 PM, johnkn63 wrote:
>> When usin
y, as it has no
direct ties to any libpq internals.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
RAC, where the masters share a
coherent cache and implement global locks.
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
First, apologies for taking so long to reply to your post.
On Fri, 22 Jun 2012 09:55:13, Robert Haas wrote:
> On Wed, Jun 20, 2012 at 12:24 PM, John Lumby
> wrote:
> > An INSERT which has a RETURNING clause and which is to be rewritten
> >based on
> > a rule
-
I attach patch based on clone of postgresql.git as of yesterday (120619-145751
EST)
I have tested the patch with INSERT and UPDATE (not tested with DELETE but
should work).
The patch is not expected to be final but just to show how I did it.
John
FYI, I was just checking out the contributors page and noticed that he's
listed under Past Contributors.
http://www.postgresql.org/community/contributors/
On Fri, Jul 8, 2011 at 1:55 PM, Bruce Momjian wrote:
> Tom Lane wrote:
> > Robert Haas writes:
> > >> Anyone feels in mood for a comment?
OK, how much are we talking about?
From: Josh Berkus
To: John Adams
Cc: PostgreSQL-development
Sent: Fri, September 3, 2010 1:07:03 PM
Subject: Re: [HACKERS] returning multiple result sets from a stored procedure
> I noticed in postgres you cannot ret
program is creative and
needs some thinking and the bulk of it is just a million stupid details.
I just don't follow/understand your thinking. Maybe I am naïve.
I do not have experience with open source and I kind of thought open source
guys
do not need or care about money and time.
I noticed in postgres you cannot return multiple result sets from a stored
procedure (surprisingly as it looks like a very good dbms).
I would like to suggest adding this feature.
- It is very usefull
- It is supported by all other dbmss I have worked with.
- makes porting applications to postg
feng tian wrote:
Hi,
I want to load balance a postgres server on 4 physical machines, say
127.0.0.11-14. I can set up a pgbouncer on 127.0.0.10 and connection
pooling to my four boxes. However, the traffic from/to clients will
go through an extra hop. Another way to do this, is to send the
Bjorn Munch wrote:
I will have a look into it.
as of right now, I suspect what I need are the following files from a
recent Solaris 64bit build...
include/server/pg_config.h
lib/64/pgxs/src/Makefile.global
there are a few more files that could be involved, but AFAIK, they are
inva
the 8.4.3 binary tarball for solaris sparc
64bit on postgresql.com was shipped with the 32bit includes and the
Makefile fragments from 8.4-community/lib/64/pgxs/src/
I'm specifically hitting this contradition:
$ grep FLOAT8 include/server/pg_config.h
#define FLOAT8PASSBYVAL false
and
Here's a fix. Sorry, I didn't realize it was ever called without a
version number.
On Wed, Jan 6, 2010 at 11:18 AM, Stefan Kaltenbrunner
> heh that's a nice one the snapshot generation script uses "
> gmake -s VERSION=snapshot dist" and that leads to getting "
> --set-version=snapshot" passed to g
FWIW, the old make rule was
fmgroids.h fmgrtab.c: (deps)
which is now
fmgroids.h: fmgrtab.c ;
fmgrtab.c: (deps)
I was going by this comment in parser/Makefile:
# There is no correct way to write a rule that generates two files.
# Rules with two targets don't have that meaning, they are merel
Tom,
It seems I introduced a couple errors in src/tools/msvc/clean.bat in
the bki patch. I'm attaching a cumulative fix. I can resend the
complete updated patch, if you like...
Sorry! :-)
John
> I'm planning to go look at Naylor's bki refactoring patch now. Assuming
ie, they are not needed to build from
>> a source tarball. Otherwise this *is* moving the goalposts on required
>> tool support.
> The patch already does that if I understood John correctly.
Yes, everything output by Perl in my patch is a distprep target.
Some minor changes would
Here's a patch:
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 6750db8..1276c39 100644
*** a/doc/src/sgml/backup.sgml
--- b/doc/src/sgml/backup.sgml
*** if (!triggered)
*** 2018,2024
!Data Definition Language (DML) - INSERT,
to
> pg_proc and that this not mean that I have to edit almost every single
> line of the damn monster file.
One could conceivably write a script against Catalog.pm that generated
DATA(); statements to copy and paste into a header file. It might be a
useful tool, if only for error checking. For
rc/include/catalog/pg_statistic.h| 259 -
src/include/catalog/pg_tablespace.h | 63 -
src/include/catalog/pg_trigger.h | 113 -
src/include/catalog/pg_trigger_fn.h | 42 +
src/include/catalog/pg_ts_config.h| 60 -
src/include/
for standardization at the
SQL level. We will keep your other remarks in mind as we proceed.
Best regards!
--
John
John MurtariSoftware Workshop Inc.
jmu
TION SCHEMA.
>
> I don't really get the point of the SHOW STATISTICS command. There is
> already a command whose purpose is to retrieve data in tabular form,
> namely SELECT.
Okay, thank you. We will take another look at those items.
Best regards!
-
tation specific.
As you can see, the goal here is reporting on activity
at the SQL level.
Regarding the GPL limitation. That will probably be
removed on code we release to PostgreSQL -- hadn't really thought
about the fact it would be a show stopper. Thanks for bringing
that u
n the tables
have more stability and are updated on an ongoing basis? If you have
any pointers to schema table creation that would be great!
Best regards!
--
John
____
John Murtar
ing real to test against.
We were trying to decided what later release to target, looks
like we'll go for 8.4 and 8.5 as staff/work permits. Any feedback on
the syntax/output is welcome.
Best regards!
--
John
_
CHEMA implementation for MySQL 5.x, but not yet for PostgreSQL.
Why this? We were a web hosting Company and were absolutely
maddened that no simple tools existed to tell us who was causing
usage spikes on a DB server shared by multiple users. We now
know!
Best regards!
--
1 - 100 of 462 matches
Mail list logo
