> "Bruce" == Bruce Momjian writes:
Bruce> Oh, right, you want date, so use:
Bruce> SELECT date_trunc('week', CURRENT_DATE) + '6 days';
Three major things wrong with this:
1. If you do this on Sunday, it gives you the current day not the _next_
Sunday.
2. If you try and do this for other
> "Ron" == Ron writes:
Ron> Hi,
Ron> v9.6.6
Ron> Is there a built in function to calculate, for example, next
Ron> Sunday?
No, but such things aren't hard to calculate using the available
primitives.
To get "next Xday", for example, you can add 7 days and then do
"previous or current
On Thu, Jan 31, 2019 at 02:21:52PM -0600, Ron wrote:
> On 1/31/19 2:15 PM, Bruce Momjian wrote:
> >On Thu, Jan 31, 2019 at 02:11:14PM -0600, Ron wrote:
> >>Hi,
> >>
> >>v9.6.6
> >>
> >>Is there a built in function to calculate, for example, next Sunday?
> >>
> >>For example,
> >>
> >>postgres=# sel
On 1/31/19 2:15 PM, Bruce Momjian wrote:
On Thu, Jan 31, 2019 at 02:11:14PM -0600, Ron wrote:
Hi,
v9.6.6
Is there a built in function to calculate, for example, next Sunday?
For example,
postgres=# select current_date, next_dow(current_date, 'Sunday');
date | date
|---
lup wrote
> On 1/31/19 12:48 PM, legrand legrand wrote:
>>
>> In all cases, developer support was premium.
>>
> Can you please expand on "support was premium". I'm not sure if that
> was the level of support purchased, or perhaps an indication that
> support was heavily used. Or have I missed it
On Thu, Jan 31, 2019 at 02:11:14PM -0600, Ron wrote:
> Hi,
>
> v9.6.6
>
> Is there a built in function to calculate, for example, next Sunday?
>
> For example,
>
> postgres=# select current_date, next_dow(current_date, 'Sunday');
> date | date
> |
> 2019-01-31
Hi,
v9.6.6
Is there a built in function to calculate, for example, next Sunday?
For example,
postgres=# select current_date, next_dow(current_date, 'Sunday');
date | date
|
2019-01-31 | 2019-02-03
(1 row)
Thanks
--
Angular momentum makes the world go 'round
On 1/31/19 12:48 PM, legrand legrand wrote:
Hi,
We have use it to "archive" 2 Oracle databases (8i and 9i)
to pg 9.5 on windows (for a target of more than 250GB).
We also use it to monitor our Oracle 11g databases,
storing some performances / capacity planning data
(like ASH, AWR, ...) in Pos
Hi,
We have use it to "archive" 2 Oracle databases (8i and 9i)
to pg 9.5 on windows (for a target of more than 250GB).
We also use it to monitor our Oracle 11g databases,
storing some performances / capacity planning data
(like ASH, AWR, ...) in Postgres.
In all cases, developer support was p
On Thu, Jan 31, 2019 at 05:37:00PM +0100, Piotr Włodarczyk wrote:
> Hi everyone,
>
> I have some question considering about oracle_fdw and safety of use it in
> production environment.
>
> Problem we would like to resolve using this extension is to move data from
> five
> Oracle tables to Postgr
Hi everyone,
I have some question considering about oracle_fdw and safety of use it in
production environment.
Problem we would like to resolve using this extension is to move data from
five Oracle tables to Postgres database. To avoid situation that we have to
trasfer data using sftp/ssh or anot
On 31/01/2019 14:58, Tom Lane wrote:
Howard News writes:
On 30/01/2019 18:08, Tom Lane wrote:
Note that if you had those functions laying around ever since 8.3,
they're probably just "loose" and not wrapped into an extension at all.
unfortunately running
create extension tsearch2 from unpac
Howard News writes:
> On 30/01/2019 18:08, Tom Lane wrote:
>> Note that if you had those functions laying around ever since 8.3,
>> they're probably just "loose" and not wrapped into an extension at all.
> unfortunately running
> create extension tsearch2 from unpackaged;
> caused the following e
On Thu, Jan 31, 2019 at 4:09 PM Achilleas Mantzios <
ach...@matrix.gatewaynet.com> wrote:
> On 31/1/19 3:55 μ.μ., Radoslav Nedyalkov wrote:
> > Hi All,
> > We want to setup a logical replica with initial load from physical
> standby. (all pg10.5)
> > Basically what we tested is:
> > 1.on the maste
On 31/1/19 3:55 μ.μ., Radoslav Nedyalkov wrote:
Hi All,
We want to setup a logical replica with initial load from physical standby.
(all pg10.5)
Basically what we tested is:
1.on the master: create publication and logical slot.
2.on the standby: pause the stanby. (lsn from 1. is already replayed
Hi All,
We want to setup a logical replica with initial load from physical standby.
(all pg10.5)
Basically what we tested is:
1.on the master: create publication and logical slot.
2.on the standby: pause the stanby. (lsn from 1. is already replayed).
3.on the standby: get last replayed lsn, pg_last
On 1/31/19 7:10 AM, Mirco Gallazzi wrote:
GoodMornig,
I can’t install postgres on my pc because i have Always this error: “
Problem running post-install step. Installation may not complete
correctly. The database cluster initialisation failed.”
I looked for a guide that can help me to solve
GoodMornig,
I can’t install postgres on my pc because i have Always this error: “ Problem
running post-install step. Installation may not complete correctly. The
database cluster initialisation failed.”
I looked for a guide that can help me to solve this problem but it was all a
big fail.
Itri
On 30/01/2019 18:08, Tom Lane wrote:
Note that if you had those functions laying around ever since 8.3,
they're probably just "loose" and not wrapped into an extension at all.
You could fix that in a 9.5 database by running
create extension tsearch2 from unpackaged;
which should be enough to
19 matches
Mail list logo
