Hi,
During the recovery process, It would be nice if PostgreSQL generates an
error by aborting the recovery process (instead of starting-up the cluster)
if the intended recovery target point is not reached and give an option to
DBA to resume the recovery process from where it exactly stopped.
The
On Mon, Aug 15, 2016 at 5:58 PM, Thomas Munro
wrote:
> Also, I have attached a v2->v3 diff ...
Ugh. I meant a v1->v2 diff.
--
Thomas Munro
http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgr
On Sun, Aug 14, 2016 at 9:04 AM, Thomas Munro
wrote:
> On Fri, Aug 12, 2016 at 9:47 AM, Robert Haas wrote:
>> [condition-variable-v1.patch]
>
> Don't you need to set proc->cvSleeping = false in ConditionVariableSignal?
I poked at this a bit... OK, a lot... and have some feedback:
1. As above,
On 2016-08-14 21:04:57 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2016-08-07 14:46:06 -0400, Tom Lane wrote:
> >> Robert Haas writes:
> >>> I think the whole idea of a fast temporary table is that there are no
> >>> catalog entries. If there are no catalog entries, then dependencies
>
Andres Freund writes:
> On 2016-08-07 14:46:06 -0400, Tom Lane wrote:
>> Robert Haas writes:
>>> I think the whole idea of a fast temporary table is that there are no
>>> catalog entries. If there are no catalog entries, then dependencies
>>> are not visible. If there ARE catalog entries, to wh
On 2016-08-07 14:46:06 -0400, Tom Lane wrote:
> Robert Haas writes:
> > I think the whole idea of a fast temporary table is that there are no
> > catalog entries. If there are no catalog entries, then dependencies
> > are not visible. If there ARE catalog entries, to what do they refer?
> > Wit
I recently had a client contact me thinking that a CREATE MATERIALIZED
VIEW had somehow managed to keep running in the background after being
^C'd in psql. Turns out this confusion was because their monitoring
eventually complained about the still open (but now aborted)
transaction. The user di
På søndag 07. august 2016 kl. 18:35:56, skrev Tom Lane mailto:t...@sss.pgh.pa.us>>:
Dean Rasheed writes:
> On 5 August 2016 at 21:48, Tom Lane wrote:
>> OK, thanks. What shall we do about Andreas' request to back-patch this?
>> I'm personally willing to do it, but there is the old bugaboo of
I did a trial run following the current pgindent README procedure, and
noticed that the perltidy step left me with a pile of '.bak' files
littering the entire tree. This seems like a pretty bad idea because
a naive "git add ." would have committed them. It's evidently because
src/tools/pgindent/p
Hello Postgres Hackers!
I sent this already a few hours ago but it got blocked because I had not
yet joined the mailing list. Trying again, sorry for any redundancy or
confusion!
This is to fix an issue that came up for me when running initdb.
At the end of a successful initdb it says:
Suc
On Tue, Nov 3, 2015 at 6:37 AM, Simon Riggs wrote:
> On 3 November 2015 at 15:23, Amit Kapila wrote:
>>
>> On Fri, Oct 23, 2015 at 6:29 AM, Simon Riggs
>> wrote:
>>>
>>> On 21 October 2015 at 13:31, Jeff Janes wrote:
>>>
Index-only scans will visit the heap for each tuple until the first
>
Aravind Kumar writes:
> when I do
> select 1.0e+1001::numeric;
> I get
> invalid input syntax for type numeric: "1.0e+1001"
> Postgresql documentation tells me that numeric data type has an upper
> limit of 131072 digits before decimal point.
You can successfully do
select pow(10::numer
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, failed
Spec compliant: tested, passed
Documentation:tested, passed
Hi hackers!
I've read the patch and here is my code review.
Hello Postgres Team!
This is to fix an issue that came up for me when running initdb.
At the end of a successful initdb it says:
Success. You can now start the database server using:
pg_ctl -D /some/path/to/data -l logfile start
but this command did not work for me because my data d
14 matches
Mail list logo
