> On Nov 1, 2017, at 1:02 PM, Nico Williams <n...@cryptonector.com> wrote:
>
> On Thu, Mar 19, 2015 at 05:41:02PM -0500, David Christensen wrote:
>> The two-arg form of the current_setting() function will allow a
>> fallback value to be returned instead of throwing
The two-arg form of the current_setting() function will allow a
fallback value to be returned instead of throwing an error when an
unknown GUC is provided. This would come in most useful when using
custom GUCs; e.g.:
-- errors out if the 'foo.bar' setting is unset
SELECT
The two-arg form of the current_setting() function will allow a
fallback value to be returned instead of throwing an error when an
unknown GUC is provided. This would come in most useful when using
custom GUCs; e.g.:
-- errors out if the 'foo.bar' setting is unset
SELECT
The HA docs reference a “glossary” link which is no longer accessible, nor is
it likely to be useful in general to link off-site IMHO. This simple patch
removes this link.
Best,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
0001-Remove-defunct
> On Mar 9, 2017, at 1:01 PM, Robert Haas <robertmh...@gmail.com> wrote:
>
> On Sun, Feb 19, 2017 at 12:02 PM, David Christensen <da...@endpoint.com>
> wrote:
>> Hi Robert, this is part of a larger patch which *does* enable the checksums
>> online; I’ve been
> Hi David,
>
> Here's a review of your patch.
Hi Ilmari, thanks for your time and review. I’m fine with the revised version.
Best,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postg
> On Feb 19, 2017, at 8:14 PM, Jim Nasby <jim.na...@bluetreble.com> wrote:
>
> On 2/19/17 11:02 AM, David Christensen wrote:
>> My design notes for the patch were submitted to the list with little
>> comment; see:
>> https://www.postgresql.org/message-id/1E6
> On Feb 19, 2017, at 5:05 AM, Robert Haas <robertmh...@gmail.com> wrote:
>
> On Fri, Feb 17, 2017 at 2:28 AM, David Christensen <da...@endpoint.com> wrote:
>> - Change "data_checksums" from a simple boolean to "data_checksum_state", an
>&
On Feb 17, 2017, at 10:31 AM, Magnus Hagander <mag...@hagander.net> wrote:
>
> On Thu, Feb 16, 2017 at 9:58 PM, David Christensen <da...@endpoint.com> wrote:
> Extracted from a larger patch, this patch provides the basic infrastructure
> for turning data
> checksums o
h will cause failures once datablocks without
> checksum starts replicating.
Good point; I’ll send a revision soon.
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
in the
cluster.
I have *not* changed the default in initdb to enable checksums, but this would
be trivial.
disable-checksums.patch
Description: Binary data
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-ha
Fixes some DESCR() grammar mistakes introduced by the xlog -> wal changes.
---
src/include/catalog/pg_proc.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/include/catalog/pg_proc.h b/src/include/catalog/pg_proc.h
index 41c12af..bb7053a 100644
---
Throws a build error if we encounter a different number of fields in a
DATA() line than we expect for the catalog in question.
Previously, it was possible to silently ignore any mismatches at build
time which could result in symbol undefined errors at link time. Now
we stop and identify the
> On Jan 23, 2017, at 10:59 AM, David Christensen <da...@endpoint.com> wrote:
>
>>
>> On Jan 23, 2017, at 10:53 AM, Simon Riggs <si...@2ndquadrant.com> wrote:
>>
>> On 23 January 2017 at 16:32, David Christensen <da...@endpoint.com> w
> On Jan 23, 2017, at 10:53 AM, Simon Riggs <si...@2ndquadrant.com> wrote:
>
> On 23 January 2017 at 16:32, David Christensen <da...@endpoint.com> wrote:
>
>> ** Handling checksums on a standby:
>>
>> How to handle checksums on a standby is a bit t
, we'll be guaranteed to have
the checksums calculated on the standby by the time it appears valid due to
system state.
We may also be able to use the WAL records to speed up the processing of
existing heap files if they are interrupted for some reason, this remains to be
seen.
** Testing changes:
We need to add separate initdb checksum regression test which are outside of
the normal pg_regress framework.
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ractical difference, WORKSFORME; I can see the point
about boxing us into a corner at some future time.
+1.
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> On May 19, 2016, at 3:17 PM, Евгений Шишкин <itparan...@gmail.com> wrote:
>
>
>> On 19 May 2016, at 22:59, Tom Lane <t...@sss.pgh.pa.us> wrote:
>>
>> David Christensen <da...@endpoint.com> writes:
>>> This simple patch adds “ALL” as an
This simple patch adds “ALL” as an EXPLAIN option as shorthand for “EXPLAIN
(ANALYZE, VERBOSE, COSTS, TIMING, BUFFERS)” for usability.
0001-Add-EXPLAIN-ALL-shorthand.patch
Description: Binary data
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via
> On Oct 9, 2015, at 2:17 PM, Robert Haas <robertmh...@gmail.com> wrote:
>
> On Thu, Oct 8, 2015 at 12:43 PM, David Christensen <da...@endpoint.com> wrote:
>> I’m happy to move it around, but If everything is in order, how will this
>> affect things
> On Oct 8, 2015, at 11:23 AM, Robert Haas <robertmh...@gmail.com> wrote:
>
> On Tue, Oct 6, 2015 at 9:15 AM, David Christensen <da...@endpoint.com> wrote:
>> Fixes a build issue I ran into while adding some columns to system tables:
>>
>>Throws a
time which could result in symbol undefined errors at link time. Now
we stop and identify the infringing line as soon as we encounter it,
which greatly speeds up the debugging process.
0001-Teach-Catalog.pm-how-many-attributes-there-should-be.patch
Description: Binary data
--
David
Use the correct name “pgindent” in comments.
0001-Make-pgindent-references-consistent.patch
Description: Binary data
--
David Christensen
PostgreSQL Team Manager
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
validation.
With “revalidating” since your database is still actively making changes, you
need to validate writes too (think new tables, etc). “Enabling” needs reads
unvalidated because you’re starting from an unknown state (i.e., not
checksummed already).
Thanks,
David
--
David Christensen
Quick comment fix for edit issue.
0001-Fix-comment.patch
Description: Binary data
--
David Christensen
PostgreSQL Team Manager
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
should support
disabling of this feature; with this proposed patch the disable action is
fairly trivial to handle.
Requesting an explicit checksum cycle would be desirable in the case where you
want to proactively verify there is no cluster corruption to be found.
David
--
David Christensen
standby WAL replay
I look forward to any feedback; thanks!
David
--
David Christensen
PostgreSQL Team Manager
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Jul 13, 2015, at 3:50 PM, Jim Nasby jim.na...@bluetreble.com wrote:
On 7/13/15 3:26 PM, David Christensen wrote:
* Incremental Checksums
PostgreSQL users should have a way up upgrading their cluster to use data
checksums without having to do a costly pg_dump/pg_restore; in particular
When encountering an initdb failure in pg_regress, we were displaying the
incorrect path to the log file; this commit fixes all 3 places this could occur.
0001-Output-the-correct-path-for-initdb.log-in-pg_regress.patch
Description: Binary data
--
David Christensen
PostgreSQL Team Manager
On Jul 7, 2015, at 3:53 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jul 7, 2015 at 2:11 AM, David Christensen da...@endpoint.com wrote:
Quickie patch for spotted missing psql \ddp tab-completion.
Thanks for the report and patch!
I found that tab-completion was not supported
Quickie patch for spotted missing psql \ddp tab-completion.
0001-Add-missing-ddp-psql-tab-completion.patch
Description: Binary data
--
David Christensen
PostgreSQL Team Manager
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers
?
- if so, does this cause any interference with frozen relations?
What additional changes would be required or what wrinkles would we have to
work out?
David
--
David Christensen
PostgreSQL Team Manager
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list
for, but I also
think there’s some benefit to be found in having it happen while the replica is
being streamed/built.
Ideas/thoughts/reasons this wouldn’t work?
David
--
David Christensen
PostgreSQL Team Manager
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql
On Mar 19, 2015, at 6:27 PM, Tom Lane t...@sss.pgh.pa.us wrote:
David Christensen da...@endpoint.com writes:
The two-arg form of the current_setting() function will allow a
fallback value to be returned instead of throwing an error when an
unknown GUC is provided. This would come in most
On Mar 20, 2015, at 11:10 AM, David G. Johnston david.g.johns...@gmail.com
wrote:
On Fri, Mar 20, 2015 at 9:04 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Mar 20, 2015 at 10:54 AM, David Christensen da...@endpoint.com
wrote:
In that case, the other thought I had here
of the function in an
exception block just to catch and utilize a default setting value
within a function.
0001-Add-two-arg-for-of-current_setting-NAME-FALLBACK.patch
Description: Binary data
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql
-for-typo-in-built-in-conversion-type-names.patch
Description: Binary data
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
785-727-1171
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
pushed upstream.
Perhaps `git notes` could be something used to annotate these:
http://www.kernel.org/pub/software/scm/git/docs/git-notes.html
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
missing something?)
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
SET datallowconn = FALSE for
the databases in question?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
to acquire the same locks without
blocking the procedure?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
things like shell expansion to work as expected:
$ ls
01-schema.sql02-data1.sql03-fixups.sql
$ psql database -- *.sql
etc.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
, it's a little awkward, but I think it's still better than adding
another keyword. Any other ideas for wording?
CHECK VALID?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
?)
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
(or it wouldn't still be
an issue), but what's wrong with the equivalent of \i in the successive .sql
upgrade files? Or is the server running the scripts itself and no equivalent
include feature exists in raw sql?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
the declaration of perl_sys_init_done; was that an
independent bug fix, or did something in the patch require that?
Cheers,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
things up.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
pointers for
toasted tuples?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
this be to manage some of the failover scenarios (i.e., setting
any relevant config from a central clusterware|whatever)?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
support specific formats). This will
allow you to navigate to the specific definition of the type/function/macro,
and can be very enlightening and help answer some of these questions. `git
grep` will also come in handy if you're working directly from a git checkout.
Regards,
David
--
David
of the standby is more-or-less tangential to the specific
registration issue.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
/REL8_5_ALPHA3_BRANCH
remotes/origin/REL9_0_ALPHA4_BRANCH
remotes/origin/REL9_0_ALPHA5_BRANCH
remotes/origin/REL9_0_STABLE
remotes/origin/master
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
for
the commit in question.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and after) were set apart with literal/ or similar.
This is already in use in some places in this patch, so seems like the correct
markup.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
if it was intentional behavior.
Thanks,
David
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and come back to it later.
Can you post the cvs2svn command line used for conversion?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
, but if it's not generally
useful to the community at large, I'll understand if it's punted.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
which explicitly includes the psqlrc file in non-interactive use
(perhaps if -x is available, use it for the analogue to -X).
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
example...
So you're working on some back branch, and make a WIP commit so you can switch
to master to make a quick commit. Create a push on master. Bare git push.
WIP commit gets pushed upstream. Oops.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
for comitting, much like
I assume all of us have today in cvs.
You can also do a rebase after the merge to remove the local merge commit
before pushing. I tend to do this anytime I merge a local branch, just to
rebase on top of the most recent origin/master.
Regards,
David
--
David Christensen
,
why not display the actual socket path in the general local socket case?
Also, while we're still tweaking this patch, I've had a couple requests for the
SSL status of the connection as well; does this seem like a generally useful
parameter to display as well?
Regards,
David
--
David
that people are
used to doing, as opposed to having to explicitly type things out or do
contortions will shell substitutions, etc.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
proposed patch.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.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 Jul 20, 2010, at 9:05 AM, Robert Haas wrote:
On Tue, Jul 20, 2010 at 10:00 AM, David Christensen da...@endpoint.com
wrote:
Sorry for the delays in response. This is fine; I think there are some
semantic questions that should still be resolved at this point, particularly
if we're
of -f and -c switches.
Otherwise it's just plain confusing.
+1.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
postgresql.conf file any more, beyond adding one line to the bottom
of it which is an include directive, to bring in our overrides.
What will make everyone happy here?
So you'll now issue:
$ initdb ... -C 'include localconfig.conf' ? :-)
Regards,
David
--
David Christensen
End Point Corporation
da
On Jul 19, 2010, at 10:34 PM, Robert Haas wrote:
On Sun, Jul 18, 2010 at 2:00 PM, David Christensen da...@endpoint.com wrote:
Updated the commitfest entry with the patch, updated the title to reflect
the actual name of the command, and marked as ready for committer.
I took a look
or the socket path should show up here still.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.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 Jul 19, 2010, at 11:10 PM, Robert Haas wrote:
On Tue, Jul 20, 2010 at 12:07 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Jul 20, 2010 at 12:02 AM, David Christensen da...@endpoint.com
wrote:
I would propose to print instead:
You are connected to database rhaas via local socket
]
machack:machack:5432=# \c foobar
You are now connected to database foobar.
As you can see, the value passed to connect differs from the output in the
connected to database string.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list
On Jul 18, 2010, at 12:17 PM, David Christensen wrote:
On Jun 21, 2010, at 9:00 AM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Jun 20, 2010 at 10:51 PM, Steve Singer ssinger...@sympatico.ca
wrote:
One comment I have on the output format is that values (ie
On Jul 18, 2010, at 12:30 PM, Tom Lane wrote:
David Christensen da...@endpoint.com writes:
machack:machack:5432=# \c foobar
You are now connected to database foobar.
What this is reflecting is that backslash commands have their own weird
rules for processing double quotes. What I
On Jul 18, 2010, at 12:33 PM, David Christensen wrote:
On Jul 18, 2010, at 12:30 PM, Tom Lane wrote:
David Christensen da...@endpoint.com writes:
machack:machack:5432=# \c foobar
You are now connected to database foobar.
What this is reflecting is that backslash commands have
of that HINT or not.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
such?
Since we're treating this as a distinct object type, instead of repeatedly
typing MATERIALIZED VIEW, is there a possibility of introducing a keyword
alias MATVIEW without complicating the grammar/code all that much, or is that
frowned upon? Paintbrushes, anyone?
Regards,
David
--
David
, and/or something that we're looking to
implement down the line?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
.
Is there anything to do about the missing tags in git? I've wished for those
to be available as well.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
to be a mnemonic for config.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
0001-Add-C-option-to-initdb-to-allow-invocation-time-GUC-.patch
Description: Binary data
initdb-dash-C.diff
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
statements (although it is no
different than the existing code in this regard).
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
psql_process_multiple_files.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
to this (obviously including documentation - this is
just the trivial code)
My bikeshed has a --psqlrc path/to/file, but +1 on the idea.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
, and are they guaranteed to have stopped
at this point? Can failing to stop prevent/delay the shutdown/restart
of the server? Etc.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
--
David Christensen
End Point Corporation
da...@endpoint.com
skip-create-lang-dupe.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
/172744.1, etc?
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.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 Feb 7, 2010, at 1:30 PM, Tom Lane wrote:
David Christensen da...@endpoint.com writes:
On Feb 7, 2010, at 11:04 AM, Tom Lane wrote:
pg_relation_filepath(regclass) returns text
which would expose the output of relpath(), ie, the $PGDATA-relative
path name of the relation.
Should
On Jan 27, 2010, at 4:01 AM, Magnus Hagander wrote:
2010/1/27 Josh Berkus j...@agliodbs.com:
On 1/26/10 3:24 PM, David Christensen wrote:
-hackers,
In the spirit of small, but hopefully useful interface improvement
patches, enclosed for your review is a patch for providing psql
interfaces.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.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 Jan 27, 2010, at 8:08 AM, Magnus Hagander wrote:
2010/1/27 David Christensen da...@endpoint.com:
On Jan 27, 2010, at 4:01 AM, Magnus Hagander wrote:
2010/1/27 Josh Berkus j...@agliodbs.com:
On 1/26/10 3:24 PM, David Christensen wrote:
-hackers,
In the spirit of small, but hopefully
:19:02 CST 2010]
machack:postgres:8555=# \q
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-
ref.sgml
index 3ce5996..b58b24d 100644
*** a/doc/src/sgml/ref/psql-ref.sgml
--- b/doc/src/sgml/ref
to address that in a future revision.
Thanks,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
regschema.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On Jan 21, 2010, at 11:48 AM, Florian Weimer wrote:
* David Christensen:
Currently, a session will look like the following:
machack:machack:5485=# show tables;
See:
\d
or \? for general help with psql commands
machack:machack:5485=#
Said formatting looks like it could
On Jan 21, 2010, at 11:56 AM, Tom Lane wrote:
David Christensen da...@endpoint.com writes:
Enclosed is a patch adding a 'regschema' OID type.
What in the world is the point of that? The regfoo types are for
things
that have schema-qualified names.
Perhaps the naming is a bit
On Jan 21, 2010, at 12:02 PM, Tom Lane wrote:
David Christensen da...@endpoint.com writes:
Should the error messages between the SHOW cases and the others be
consistent (ERROR: unsupported command or similar)? It's worth
noting that this is only in the psql client, but we could simulate
^Wbe gentle. I obviously
don't expect this to not promote a wild debate/flamewar... ;-) The
formatting and specific wording for the various messages are totally
up-in-the-air, and gladly up for debate.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
diff
SQL syntax. The exact wording/output of the
messages can be adjusted at whim.
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
in usability for those people. Deciding
to support this small subset does not obligate you to expand the scope
in the future. (Hey ma, this slope ain't slippery!)
Regards,
David
--
David Christensen
End Point Corporation
da...@endpoint.com
--
Sent via pgsql-hackers mailing list (pgsql
On Jan 19, 2010, at 3:12 PM, Andrew Dunstan wrote:
David Christensen wrote:
+ if (MYSQL_HELP_CHECK(use))
+ {
+ MYSQL_HELP_OUTPUT(\\c database);
+ }
[snip]
+ else
On Jan 19, 2010, at 3:39 PM, Tom Lane wrote:
David Christensen da...@endpoint.com writes:
On Jan 19, 2010, at 2:58 PM, Stefan Kaltenbrunner wrote:
well those are the most common ones I guess for the current version
of the mysql commandline client - but what about future versions or
the fact
1 - 100 of 105 matches
Mail list logo