when
you start considering namespaces, that anything we can do to simplify
common use cases can only help improve the uptake of postgres xml.
Thanks,
--
Mike Fowler
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
e to attempt to parse the xpath_expression looking for
XQuery style namespace declartions. So I think we ignore declared
namespace support for the moment and just get the syntax correct ready
for XQuery support in the hopefully near future.
Do you agree with what I have proposed?
Regards,
hat we
> have to first ADD PARTITION then swap the table and the partition.
> Thoughts?
>
> MERGE
> -
>
> You can merge and list partitions and any two range partitions:
>
> ... MERGE , [INTO PARTITION ]
>
> For range partitions:
>
> ... MERGE PARTITION FOR(date '2006_01_01'), PARTITION FOR(date '2007-01-01');
>
> For list partitions:
>
> ... MERGE PARTITION FOR(VALUES('CA', 'MA')
>
> This begs the question of why we have COALESCE for hash partitioning. I
> don't know, it just seems like the right thing since you can't merge two
> hash partitions together (well, you shouldn't want to).
>
> RENAME
> --
>
> Rename a partition. We can use partition name or FOR clause.
>
> SPLIT
> -
>
> Split is used to divide a partition in two. It is designed for list and
> range partitioning but I guess we could/should support hash. I need to
> think about that. For RANGE partitions:
>
> ... SPLIT [INTO (PARTITION ,
> PARTITION )];
>
> AT clause specifies the point at which the partition is split in two:
>
> ... SPLIT PARTITION FOR(2000) AT 1000 INTO PARTITION (part1000,
> part2000)
>
> We might want ways to do this with unnamed partitions, it seems to me.
> Thoughts?
>
> For list:
>
> ... SPLIT PARTITION region_east AT( VALUES ('CT', 'MA', 'MD') )
> INTO
> (
> PARTITION region_east_1,
> PARTITION region_east_2
> );
>
> In this case, values from region_east specified in the AT() list are put in
> region_east_1 and the rest are put in region_east_2.
>
> I think a better way for supporting split with hash is via ADD. I'm sure
> some people think that ugly so I'd like feedback.
>
> TRUNCATE
>
>
> Truncate a specified partition:
>
> ... TRUNCATE PARTITION FOR ('2005-01-01')
>
> We could specify a name too.
>
> This will use truncate internally.
>
> ---(end of broadcast)---
> TIP 6: explain analyze is your friend
--
Mike <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
ther suggestion on where to get the data? (I'm trying
to avoid doing it using triggers).
Thanks,
Mike
On Wed, May 28, 2008 at 8:30 PM, Mike <[EMAIL PROTECTED]> wrote:
>> When you say a bit of decoding, is that because the data written to the
logs
>> is after the query parser/planner? Or because it's written in several
>> chunks? Or?
>
>Because that's the
On Wed, May 28, 2008 at 7:11 PM, Mike <[EMAIL PROTECTED]> wrote:
>> Can somebody point to the most logical place in the code to intercept the
>> WAL writes? (just a rough direction would be enough)
>
>XLogInsert
>
Great- I'll take a look at that code.
>>
>On Wed, May 28, 2008 at 8:30 PM, Mike <[EMAIL PROTECTED]> wrote:
>> When you say a bit of decoding, is that because the data written to the
logs
>> is after the query parser/planner? Or because it's written in several
>> chunks? Or?
>
>Because that's t
development and likely will change several times before or if its
finally committed for 8.5.
--
Mike
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> Maybe I'd be interesting to add development docs URL [1] so testers
> can easily find the syntax of new features, or given that they'll be
> downloading the alpha tarball they should use that documentation?
>
> [1] http://developer.postgresql.org/pgdocs/postgres/index.htm
ine, but just
having this information available increases the usefulness of such an
"outside" tool many times.
Again though, at the very least I think the raw query needs to be
included.
--
Mike
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
Is ther any info on using toast as of yet,
and if so where is it hidden
to?
Is ther any info on using toast as of yet,
and if so where is it hidden
to?
olding up beta2 for.
Will RPM's be made availiable for this beta release?
Mike
I import some of my data into my postgres database, win32 platform, via
the COPY table FROM with CSV. My CSV file is created from a Crystal
Report (v.9). I run the report and have Crystal export the results into
a CSV file (using the default settings).
I have some data which looks like this when
around this by pre-normalizing
strings matching /(\d+)-(\d+)/ into two numbers separated by a space
instead of a hyphen, but if fixing this bug would remove the need for
such a preprocessing step it would be a great help to us. Would such
strings be parsed "properly" into lexems of the form o
?
>
At least for this English speaker, substring_similarity is not
confusing even if it's not internally accurate, but English is a
strange language.
Because I want the bike shed to be blue, how does
query_string_similarity sound instead? If that's overly precise, then
word_similarit
of the most complex business logic would be simplified nearly to the
point of triviality.
Anyway, that's my $0.02.
Thank you, Anton and Peter!
-- Mike
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
st=DBD-Pg+3.5.3
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnelley.com
<http://www.rrdonnelley
this. Presumably we'd just extend existing
object_access_hooks to cover partitioned tables?
>
> This is an issue which should be resolved for PG10, so I'll add it to
> the open items list.
I'll grab it. Thanks.
--Mike
--
Sent via pgsql-hackers mailing list (pgsql-
hat's indeed the case, I wonder if
it's possible to
re
phrase the termination message
so it does not
suggest
an admin was involved.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
.git -- In both the commit message and
docs, I made note of the backwards compatibility change. I don't know
how much of an impact this would have but I suspect not many
applications are really going to be affected by how decades are counted
(should be simple to fix on their part, if any ar
On Sat, 2014-08-02 at 15:15 +1200, Gavin Flower wrote:
> Since there was no year zero: then it follows that the first decade
> comprises years 1 to 10, and the current Millennium started in 2001 - or
> am I being too logical??? :-)
This is pretty much the reason I'm sending this patch, because
On Fri, 2014-08-01 at 22:28 -0700, Mike Swanson wrote:
> I'd also argue that the current function basing the logic from
> definition #2 has limited use even when you want to use it for such.
> If you want to generate text for '(decades)s' you'd have to do:
> SELEC
ter hook in
StoreCatalogInheritance1. It seems like it may just be an issue of
adding the RELKIND_PARTITIONED_TABLE to sepgsql_relation_post_create.
--
Mike Palmiotto
Software Engineer
Crunchy Data Solutions
https://crunchydata.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Mar 27, 2017 at 11:46 AM, Robert Haas wrote:
> On Mon, Mar 27, 2017 at 11:22 AM, Mike Palmiotto
> wrote:
>> On Mon, Mar 27, 2017 at 10:47 AM, Robert Haas wrote:
>>> On Thu, Mar 9, 2017 at 9:47 AM, Stephen Frost wrote:
>>>> While going over the contri
On Mon, Mar 27, 2017 at 12:09 PM, Mike Palmiotto
wrote:
> On Mon, Mar 27, 2017 at 11:46 AM, Robert Haas wrote:
>>
>> Note that sepgsql hasn't been updated to work with RLS yet, either,
>> but we didn't regard that as an open item for RLS, or if we did the
>&g
On Fri, Mar 31, 2017 at 2:14 PM, Mike Palmiotto
wrote:
> On Mon, Mar 27, 2017 at 12:09 PM, Mike Palmiotto
> wrote:
>> On Mon, Mar 27, 2017 at 11:46 AM, Robert Haas wrote:
>>>
>>> Note that sepgsql hasn't been updated to work with RLS yet, either,
>>&g
On Fri, Mar 31, 2017 at 8:23 PM, Robert Haas wrote:
> On Fri, Mar 31, 2017 at 2:14 PM, Mike Palmiotto
> wrote:
>> Attached you will find two patches, which were rebased on master as of
>> 156d388 (applied with `git am --revert [patch file]`). The first gets
>> rid of some
me in 30 minutes from now, after I have gotten
> my first cup of coffee ;-)
After some discussion off-list, I've rebased and udpated the patches.
Please see attached for further review.
Thanks,
--
Mike Palmiotto
Software Engineer
Crunchy Data Solutions
https://crunchydata.com
From be692f
atch suggestion, except that we can replace
> the parenthetical comment with something like "(We don't care if
> redefines "true"/"false"; those are close enough.)".
>
Sounds good. Updated patchset will include that verbiage, along with
some regression tests
On Wed, Apr 5, 2017 at 1:22 PM, Mike Palmiotto
wrote:
> On Wed, Apr 5, 2017 at 1:19 PM, Tom Lane wrote:
>> Peter Eisentraut writes:
>>> On 4/5/17 12:04, Tom Lane wrote:
>>>> Conclusion: Fedora's gcc is playing fast and loose somehow with the
>>>>
expect we'll
> have those by end of today and be able to commit the rest tomorrow.
Attached are the regression test updates for partitioned tables.
Thanks,
--
Mike Palmiotto
Software Engineer
Crunchy Data Solutions
https://crunchydata.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Jun 5, 2017 at 10:36 AM, Robert Haas wrote:
> On Mon, Jun 5, 2017 at 10:20 AM, Joe Conway wrote:
>> Unless Robert objects, I'll work with Mike to get a fix posted and
>> committed in the next day or two.
>
> That would be great. Thanks.
I have the upda
On Tue, Jun 6, 2017 at 4:07 PM, Joe Conway wrote:
> On 06/06/2017 11:57 AM, Mike Palmiotto wrote:
>> On Mon, Jun 5, 2017 at 10:36 AM, Robert Haas wrote:
>>> On Mon, Jun 5, 2017 at 10:20 AM, Joe Conway wrote:
>>>> Unless Robert objects, I'll work with Mike to
On Tue, Jun 6, 2017 at 9:12 PM, Michael Paquier
wrote:
> On Wed, Jun 7, 2017 at 9:52 AM, Joe Conway wrote:
>> Thanks Mike. I'll take a close look to verify output correctnes, but I
>> am concerned that the new tests are unnecessarily complex. Any other
>> opinions on
On Wed, Jun 7, 2017 at 9:49 AM, Mike Palmiotto
wrote:
> One thing that concerns me is the first EXPLAIN plan from regress_rls_dave:
> +EXPLAIN (COSTS OFF) SELECT * FROM part_document WHERE f_leak(dtitle);
> + Q
Something like that would be helpful. I just had to stop one after an
hour and have no idea how much longer it would have taken.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR
David wrote:
> I believe there are ways to get perlcritic to keep quiet about things
> we don't find relevant. Maybe that's a better way to use it.
>
There are indeed. A .perlcriticrc file can suppress (or add) either
individual rules or groups of rules. I use one to ignore the ones I
dis
ewhere?
It appears the doc install correctly creates 'share', so installing src/bin
last works.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave |
is a patch to add a note to the docs mentioning this fact.
______
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313
Robert,
Thanks for the reply. I have no objections to clarifying the note.
Attached is a patch with the text you suggested.
Mike
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management
I'd received an email from Gibheer suggesting it be move due to lack of time to
work on it. I can certainly move it back if that's no longer the case.
On Oct 9, 2013, at 23:25, Amit Kapila wrote:
> On Thu, Oct 10, 2013 at 3:17 AM, Gibheer wrote:
> On Mon, 7 Oct 2013 11:39:55 +0530
> Amit
!
Mike Blackwell
On Tue, Oct 15, 2013 at 1:39 AM, Noah Misch wrote:
> On Mon, Oct 14, 2013 at 01:56:42PM -0500, Mike Blackwell wrote:> Any
> patches marked Needs Review will be automatically moved to the next CF.
> > We will try to make sure that all patches in the current CF have
> receive
much difference.
______
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
se going on here?
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonne
I added this to the current CF, and am starting to review it as I have time.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174
is, though.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnelley.c
scenarios, etc?
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnell
On Wed, Oct 23, 2013 at 2:10 PM, Atri Sharma wrote:
>
> Adding myself as the co reviewer specifically for the testing
> purposes, if its ok with you.
>
It's perfectly fine with me. Please do!
___
s.
Still to be tested:
the counts for streaming replication (no replication setup here to test
against yet).
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 W
Also still to be tested: performance impact.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
uld you
expect separate CF entries for the refactoring and the fix?
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnelley.com
<http://www.rrdonnelley.com/>
* *
Writing a Foreign Data Wrapper and interested in isolating the WHERE clause
to speed up the access of an indexed file on my filesystem. I'm attempting
to understand the inner workings of how the data is retrieved so I'm
writing code to just handle one case at the moment: WHERE clause on a
single co
your previous question about sequences there are 61K in the
DB, looks like our schema currently has about 115 sequences per tenant.
--Mike
>
>
> I'm just pulling another backup using the stock 9.1.1 pg_dump to ensure
> the backups are equivalent.
>
> Schema & data are identical between the 2 backups. the new backup passes
all our tests for validating a tenant.
Thank you again for the quick response!
--Mike
:) yah that makes sense no big deal. i'll probably just push this head
buiild of pg_dump onto the production machines till it comes out.
Thanks again!
On Sat, Mar 31, 2012 at 3:44 PM, Tom Lane wrote:
> Mike Roest writes:
> > Any idea when 9.1.4 with this change will be out
c/postgres.patched.v3/src/test/regress'
make: *** [check] Error 2
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnelley.com
<http://www.rrdonnelley.com/>
* *
he GUC variable
'wal_update_compression_ratio'?
______
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mi
believe Atri will be looking at that.
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.bl
The only environment I have available at the moment is a virtual box.
That's probably not going to be very helpful for performance testing.
______
*Mike Blackwell | Technical Analyst, Distribution Services/Ro
>
>
>> On 18 November 2014 21:19, Petr Jelinek wrote:
>>
>> Personally, I see this as natural extension of the conditional block
>>> control
>>> which we already have for loops with CONTINUE WHEN and EXIT WHEN. This
>>> basically extends it to any block and it seems quite natural to have it
>>> f
__
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnelley.com
<http://www.rrdonnelley.com/>
* *
the odbcBeginForeignScan() and odbcIterateForeignScan(), and
odbcGetQual() functions.
Thanks
On Fri, Nov 13, 2015 at 1:24 PM, Corey Huinker
wrote:
> On Fri, Nov 13, 2015 at 1:46 PM, Big Mike wrote:
>
>> Writing a Foreign Data Wrapper and interested in isolating the WHERE
>>
gt; chapter
5 covers most of them.
______
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
mike.blackw...@rrd.com
http://www.rrdonnelley.com
<http://www.rrdonnelley.com/>
* *
ng(255) | Hello
width : numeric(6,3) | 3.220
Has anyone else thought this was a missing feature?
-Mike
temp_15.t"
Column| Type| Modifiers
-+---+---
g | geometry(Polygon) |
st_centroid | geometry |
-Mike
On further review this particular server skipped from 9.2.2 to 9.2.4. This
is my most busy and downtime sensitive server and I was waiting on a
maintenance window to patch to 9.2.3 when 9.2.4 dropped and bumped up the
urgency. However, I have 3 other less busy production servers that were
all run
Looks like psql> vacuum (verbose, analyze) is not reflecting in
pg_stat_user_tables as well in some cases. In this scenario I run the
command, it outputs all the deleted pages etc (unlike the vacuumdb -avz
analyze that seemed to be skipped in the log), but it does not update
pg_stat_user_tables.
nteger
> AS 'DIRECTORY/funcs', 'add_one'
> LANGUAGE C STRICT;
>
> CREATE FUNCTION add_one(integer) RETURNS integer
> AS 'My::Package', 'add_one'
> LANGUAGE plperl STRICT;
>
+1, fwiw
--
Mike Rylander
| VP, Research and Design
| E
er_id = $1 and follower_ids
@> ARRAY[$2])
union all
(select false)
limit 1
;
$$;
Full sql is here if you need more info:
http://github.com/mikelikespie/followships/blob/c1a7e8c16159018d7d1154a11169315ac6560178/followships_2.sql
(please
forgive the sloppiness, I haven't c
t a matter of scanning for multi-byte sequences and
replacing those with their \u equivalents. I have some simple and
fast code I could share, if it's needed, though I suspect it's not.
:)
UPDATE: Thanks, Robert, for pointing to the RFC.
--
Mike Rylander
| VP, Research a
On Sun, Mar 28, 2010 at 8:33 PM, Robert Haas wrote:
> On Sun, Mar 28, 2010 at 8:23 PM, Mike Rylander wrote:
>> In practice, every parser/serializer I've used (including the one I
>> helped write) allows (and, often, forces) any non-ASCII character to
>> be encoded as
I noticed while doing work with very large arrays that several
functions such as array_length detoast the entire array instead of
only what is required.
I found the solution to be just unpacking the header portion of the
array and ignoring the rest. Since the header (including the
dimensions) is
Woops. I sent the wrong patch. My apologies. Attached is the real
patch. Sorry, also forgot this is made against 9.0 alpha 4 tag.
Thanks,
Mike
--
Michael Lewis
lolrus.org
mikelikes...@gmail.com
On Wed, Mar 31, 2010 at 12:39 AM, Mike Lewis wrote:
> I noticed while doing work with very la
On Wed, Mar 31, 2010 at 8:28 AM, Robert Haas wrote:
>
> Neat. Please add it here:
>
> https://commitfest.postgresql.org/action/commitfest_view/open
>
> ...Robert
>
Thanks. Added it.
https://commitfest.postgresql.org/action/patch_view?id=292
-Mike
--
Sent via pgsql
ms, not
> humans.
> * Output is expected to be valid JSON and work anywhere JSON should work.
> * Strict JSON is what more people would expect, I'd think.
+1
--
Mike Rylander
| VP, Research and Design
| Equinox Software, Inc. / The Evergreen Experts
| phone: 1-877-OPEN-
o far. It violates the JS part of JSON ...
> I don't think we should because doing so would be rather zany. It
> would mean JSON content could be invalid in value context, as in:
>
> // JavaScript
> var content = "key" : "value";
>
Right.
Thanks, Joseph. I
t better off getting some code
together for general review?
Thanks,
--
Mike Fowler
Registered Linux user: 379787
"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'
--
Sent via pgsql-hack
Peter Eisentraut wrote:
On ons, 2010-04-28 at 15:21 +0100, Mike Fowler wrote:
xpath_exists() is needed. It checks, whether or not the path specified
exists in the XML value. (W/o this function we need to use weird
"array_dims(xpath(...)) IS NOT NULL" syntax.)
That sou
t better off getting some code
together for general review?
Thanks,
--
Mike Fowler
Registered Linux user: 379787
"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'
--
Sent via pgsql-hack
is happy I've not regressed anything.
Can I confirm that contrib/xml2 is deprecated and I should be carrying
out my work in backend/utils/adt/xml.c?
I shall be coding it up over the next day or two, work & family permitting!
Thanks,
--
Mike Fowler
Registered Linux user: 379787
ch to the list (replying to this email is fine)
and add it here:
https://commitfest.postgresql.org/action/commitfest_view/open
Will do once I've finished. Thanks for your feedback.
Regards,
--
Mike Fowler
Registered Linux user: 379787
--
Sent via pgsql-hackers mailing list (pgs
mit, which it isn't. But if we name it
> something like:
>
> # -1 = no timeout
> # 0 = kill conflicting queries immediately
> # > 0 wait for N seconds, then kill query
> standby_conflict_timeout = -1
>
> it's more clear that the setting is a timeout for each *c
in advance for any and all feedback,
--
Mike Fowler
Registered Linux user: 379787
"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'
Index: src/backend/utils/adt/xml.c
===
) are and the data
types of the elements, simply by removing the redundant object keys.
This function would be extremely useful to me when creating or
persisting raw class instances of these sorts.
--
Mike Rylander
| VP, Research and Design
| Equinox Software, Inc. / The Evergreen Experts
| phone:
different.
Thanks,
--
Mike Fowler
Registered Linux user: 379787
"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
e up
on Oracle?
Thanks,
--
Mike Fowler
Registered Linux user: 379787
"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
Pavel Stehule wrote:
2010/5/19 Mike Fowler :
Pavel Stehule wrote:
see google: lateral sql injection oracle NLS_DATE_FORMAT
I would to like this functionality too - and technically I don't see a
problem - It's less than 100 lines, but I don't need a new security
problem.
he required
support for schema validation so I'll just be wrapping it's
functionality much like I did for xpath_exists().
Anyone got any thoughts before I get busy?
Thanks,
--
Mike Fowler
Registered Linux user: 379787
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
rate this into quorum commit
> to express 3 of 5 "reporting" standbys, 1 "berlin" standby and 1 "tokyo"
> standby from a group of multiple per data center, or even just utilize role
> sizes of 1 if you wanted individual standbys to be "named" in th
an outline design you could share
on how you would go about adding schema validation?
Regrads,
--
Mike Fowler
Registered Linux user: 379787
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
password. To me this is a feature that will just make life a
little more pleasant for command line junkies like me.
Regards,
--
Mike Fowler
Registered Linux user: 379787
NB: Post attmpt two, yesterday's was never delievered to hackers so apologies
if Alastair and Hitoshi have seen this messa
password. To me this is a feature that will just make life a
little more pleasant for command line junkies like me.
Regards,
--
Mike Fowler
Registered Linux user: 379787
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
uld be OK to use against 9
before the 9 version was stable.
Regards,
--
Mike Fowler
Registered Linux user: 379787
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ms" on my machine - one for 1.4, one for 1.5 and
one for 1.6. It's been a while since I've had an excuse to write some
Perl! I can't guarantee when I'll have it done as I'm away for a little
over a week from Wednesday and I'm not allowed internet access!
Regard
(HEAD) and 8.4.7. For each database version I build and the tests
running JDKs 1.4.2_19, 1.5.0_22 and 1.6.0_2. All on 32-bit.
Regards,
--
Mike Fowler
Registered Linux user: 379787
Index: doc/pgjdbc.xml
===
RCS file: /cvsroot/jdbc/pgj
I use tables all the time that have sequences on smallint's;
I'd like to simplify my create files by not having to create the sequence
first, but I also don't want to give up those 2 bytes per column!
Can this be added?
Mike
--- postgresql-9.0.4/src
ct
);
Where our "data" table has ~700 million rows right now.
And yes- I guess there's nothing to stop me from using a smallint in the
data table (thus getting the size savings), and reference a int in the stuff
table, but it seems like bad form to me to have a foreign key
Sorry, forgot the documentation- I guess that stuff doesn't magically
happen!
New patch attached.
Mike
From: Brar Piening [mailto:b...@gmx.de]
Sent: Tuesday, June 07, 2011 6:58 PM
To: Mike Pultz
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] smallserial / serial2
O
1 - 100 of 495 matches
Mail list logo
