Hi,
The following rather contrived example illustrates that lag(), lead()
(and probably other functions) can't automatically cast an integer to
a bigint:
select lag(sum,1,0) over () from (select sum(generate_series) over
(order by generate_series) from generate_series(1,10)) x;
ERROR: function l
On 27 Jun 2017, at 17:06, Merlin Moncure wrote:
>
>> On Tue, Jun 27, 2017 at 10:01 AM, Colin 't Hart wrote:
>> Hi,
>>
>> The following rather contrived example illustrates that lag(), lead()
>> (and probably other functions) can't automatically cast a
Hi,
git status says that I'm on branch master.
psql reports 9.3devel, yet I expected it to report 9.4devel
Is this expected behaviour? I've looked at the developer's FAQ and Wiki but
couldn't find anything about this.
Cheers,
Colin
make distclean & ./configure & make & sudo make install
helped.
Cheers,
Colin
On 21 October 2013 14:25, Michael Paquier wrote:
> On Mon, Oct 21, 2013 at 9:09 PM, Colin 't Hart
> wrote:
> > git status says that I'm on branch master.
> > psql repor
Hi,
According to http://www.postgresql.org/docs/9.3/static/sql-select.html#SQL-TABLE
"
The command
TABLE name
is completely equivalent to
SELECT * FROM name
It can be used as a top-level command or as a space-saving syntax
variant in parts of complex queries.
"
However, this isn't true:
Hi,
I can't get Postgresql to execute a query with EXCEPT (or INTERSECT)
as an anti-join (or join).
Is this even possible?
If not currently possible, is this something we would like to have?
Cheers,
Colin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On 11 November 2013 14:34, Tom Lane wrote:
> "Colin 't Hart" writes:
>> I can't get Postgresql to execute a query with EXCEPT (or INTERSECT)
>> as an anti-join (or join).
>
>> Is this even possible?
>
> No, and it probably won't ever be,
On 11 November 2013 15:16, Tom Lane wrote:
> "Colin 't Hart" writes:
>> On 11 November 2013 14:34, Tom Lane wrote:
>>> No, and it probably won't ever be, since the semantics aren't the same.
>>> EXCEPT/INTERSECT imply duplicate elimination.
On 11 November 2013 15:03, Tom Lane wrote:
> "Colin 't Hart" writes:
>> I would've thought it was implemented as a shortcut for "SELECT *
>> FROM" at the parse level (ie encounter "TABLE" and insert "SELECT *
>> FROM" into th
Hi,
I've been reading
wiki.postgresql.org/images/2/25/Full-text_search_in_PostgreSQL_in_milliseconds-extended-version.pdf
with interest and am wondering if these patches ever made it in to the
"official" version of Postgresql?
I've tried doing some of the queries as described in the slides using
Hi,
Here's a new version of a small patch to psql I'm using locally.
It adds a command \ns to psql which is a shortcut to set the
SEARCH_PATH variable.
I'd like to make a case for including this patch as it makes use of
schemas/namespaces much easier. There was resistance to including this
befor
Hi,
Attached please find a trivial patch for psql which adds a \n meta command
as a shortcut for typing set search_path =.
This allows you to navigate a database very quickly in psql as follows:
\dn
\n my_schema
\d
\d my_table
etc.
Not yet done: updating documentation (psql internal help,
Hi,
Attached please find a trivial patch for psql which adds a \n meta command
as a shortcut for typing set search_path =.
This allows you to use psql as follows:
\dn
\n my_schema
\d
\d my_table
etc.
Not yet done: updating documentation (psql internal help, psql man page,
main documentatio
On 10 July 2012 18:00, Tom Lane wrote:
> Josh Kupershmidt writes:
> > On Tue, Jul 10, 2012 at 2:09 AM, Colin 't Hart
> wrote:
> >> Attached please find a trivial patch for psql which adds a \n meta
> command
> >> as a shortcut for typing set search_path
On 10 July 2012 18:24, David Fetter wrote:
> On Tue, Jul 10, 2012 at 12:00:06PM -0400, Tom Lane wrote:
> > Josh Kupershmidt writes:
> > > On Tue, Jul 10, 2012 at 2:09 AM, Colin 't Hart
> wrote:
> > >> Attached please find a trivial patch for psql wh
Hi,
I note that the implementation of tab completion for SET TRANSACTION in PSQL
could benefit from the implementation of autonomous transactions (also
TODO).
Regards,
Colin
Hi,
Back in 2002 these were proposed, what happened to them?
http://archives.postgresql.org/pgsql-sql/2002-09/msg00406.php
Also I note:
co...@ruby:~/workspace/eyedb$ psql
psql (8.4.4)
Type "help" for help.
colin=> select to_date('731332', 'YYMMDD');
to_date
1974-02-01
(1 row)
On 20 September 2010 16:54, Andrew Dunstan wrote:
>
>
> On 09/20/2010 10:29 AM, Colin 't Hart wrote:
>>
>> Hi,
>>
>> Back in 2002 these were proposed, what happened to them?
>>
>> http://archives.postgresql.org/pgsql-sql/2002-09/msg00406.php
&
Bruce,
To query for Postgresql services on Windows use:
sc query type= service | find "postgresql"
On my machine this yields:
SERVICE_NAME: postgresql-9.0
DISPLAY_NAME: postgresql-9.0 - PostgreSQL Server 9.0
NB the space after type= is very important, don't ask me why...
I prefer to use '
Oops.
Apparently type= service is the default, so we can remove that bit.
Then we should add state= all. The default = active, a third option = inactive.
So:
sc query state= all
should list all services, in all states.
And then we pipe to find which is the Windows equivalent of grep, but
it n
Hi,
While trying to find instructions to build documentation, I noticed
that the links in README.git are broken, both redirect to
http://www.postgresql.org/docs/devel/static/
In addition, why isn't INSTALL stored in git?
Cheers,
Colin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
David et al,
How about something like this?
Cheers,
Colin
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index e603b76..a68014b 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -33,13 +33,14 @@ PostgreSQL documentation
[ WITH [ RECUR
Hi,
While looking at the documentation on SELECT I noticed that the
entries in reference.sgml aren't sorted correctly -- psql \h does have
them in the correct order.
Attached a trivial patch to fix this.
In addition, reference.sgml doesn't have entries for TABLE or WITH
which should link to ref/
Hi,
I hope this is the best place to report this or should I be on
pgsql-general or pgsql-bugs?
It seems that the order of columns in a query can make a difference in
execution times.
In my brief investigation, queries on table(a,b,c,d,e,f,g,h) of the form
select * from table order by non-inde
PS
I should have mentioned that it wasn't me that discovered this but
"Evgeny" on dba.stackexchange
He was reporting a much greater disparity in times.
See
http://dba.stackexchange.com/questions/102403/why-is-select-much-faster-than-selecting-all-columns-by-name
Thanks,
Colin
--
Sent via pgs
> Should we add this to /contrib?
I think so, at least until we get something better.
Cheers,
Colin
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so t
We could install the Postgres version of Bugzilla.
Yes, there's a version that runs on Postgres rather than MySQL.
That way we don't have to maintain the bug system.
> Ok the functionality as well as the menu item are gone. You do realize
> it's going to give the impression that we're trying to
Philip Warner wrote:
> I don't think this is a good solution. We really do need a list of bugs.
We
> probably need to list status and the releases they apply to.
Bugzilla can do this -- it has the concept of a Milestone and a Version.
> I don't think anybody but the most naieve (or biased) user
Matthew T. O'Connor volunteered:
> I don't know what a kibo is, but I would be willing to put in some time
> helping maintaing a bug reporting system. One of the helpful things with
> bugzilla setup with some other big projects is that the bug gets assigned
to
> a developer and the bug submitter
Jan Wieck said:
> > Has anyone thought of using Bugzilla? (It is MySQL based, of course) but
it
> > might answer the bug database issues. (If you guys want a bug database)
>
> Bug tracking software that doesn't use transactions and
> referential integrity in a multiuser environment?
Vince asks:
> Everybody keeps saying bugzilla. What EXACTLY will bugzilla do for us
> that would make me want to learn it and install it? BTW, the current
> wheel was invented a year ago 'cuze nothing really fit what we needed.
The reasons I would choose Bugzilla:
1. It's *not* written by us
Marc wrote:
> Actually, the 'multi-day' delay is generally related to posts from ppl
> that aren't subscribed to the lists that I have to approve manually ...
Is there a quick(er) way to 'subscribe, set nomail' on all the mailing lists
that are mirrored to news.postgresql.org?
I prefer to read/p
Ian Lance Taylor (& others) wrote:
> > This is true. However, a process-pool architecture would benefit
Postgres
> > on other platforms besides Windows. Postgresql has been ported to the
> > HP3000 MPE/iX operating system, for example, which is POSIX-compliant,
but
> > has an awfully slow fork(
33 matches
Mail list logo
